npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@requestly/modheader-export-backup

v1.0.0

Published

Export ModHeader profiles from browser storage into ModHeader's own JSON format, for import into Requestly

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nsrcodesnsrcodeswrongsahilwrongsahilsagarsoni7sagarsoni7

Keywords

modheaderrequestlyhttp-headersexportbackupchrome-extensionleveldb

Readme

modheader-export-backup

Export your ModHeader profiles without ModHeader.

npx @requestly/modheader-export-backup

Overview

ModHeader was pulled from the Chrome Web Store and Edge Add-ons in mid-2026, so its Export → Download JSON button is out of reach — you can't export from an extension you can't open.

Your profiles are still sitting in your browser profile on disk. This CLI reads them and writes the exact same export file ModHeader would have, which Requestly imports directly.

How to export

1. Run it

npx @requestly/modheader-export-backup

Needs Node.js 20 or newer. Nothing is installed permanently, and you can leave your browser open — nothing is written to your browser profile.

2. Pick a browser profile

It lists every browser profile on your machine that has ModHeader data. Move with the arrow keys and press enter.

Found 2 ModHeader backups. Which one?

  BROWSER  BROWSER PROFILE  MODHEADER PROFILES IN IT
❯ chrome   Testing          2 profiles: Profile 1, Profile 2
  edge     Person 2         1 profile: Profile 1
  Quit

up/down move · enter select · esc cancel

One row per browser profile: which browser, which of that browser's profiles, and what ModHeader has stored in it.

3. Choose where to save it

Press enter for ~/Downloads, or type another folder.

Export to [/Users/you/Downloads]

It writes modheader-<browser>-<profile>.json and returns to the list with that row marked ✓ exported, so you can repeat steps 2–3 for your other profiles. Choose Done when you have them all.

4. Import into Requestly (optional)

Your profiles are safely exported at this point — that file is yours to keep, or to import wherever you like.

If you're looking for an alternative to ModHeader, Requestly imports these files directly:

app.requestly.io/import-from-modheader

Each ModHeader profile becomes a Requestly group, carrying its request and response headers, cookie and CSP headers, redirects, and URL filters.

Browsers supported

  • Chrome — stable, Beta, Dev, Canary
  • Chromium
  • Edge
  • Brave
  • Vivaldi
  • Opera
  • Arc
  • Dia

All user profiles of each are scanned, and sideloaded or unpacked copies of ModHeader are picked up too.

Firefox is not supported — it stores extension data in a completely different format.

Nothing found?

  • Run it with --list to see every store that was detected.
  • If your browser runs with a custom profile location, point at it with --user-data-dir <path>.
  • If ModHeader was fully uninstalled a while ago, your browser may have already deleted its storage — in which case there is nothing left to recover.

Scripting it

export does the same thing without prompting, and takes --browser, --profile, --output and friends. Run --help for the full list.

npx @requestly/modheader-export-backup export --browser chrome --profile Testing --output modheader.json

Your exported data

Exported files contain whatever your ModHeader profiles contained, which often means Authorization headers and session cookies. Treat them like credentials, and don't commit them anywhere.

Development

npm install
npm start          # the interactive CLI
npm test           # end-to-end test against the real extension

License

MIT