Js Sourcemap Extract
Recover the original, un-minified sources from a JavaScript source map's sourcesContent — turning a bundled/minified .js back into a readable file tree. Accepts a .map (JSON) or a .js that references one via //# sourceMappingURL (inline data: map or sibling .map). Pure stdlib, read-only; path-traversal guarded (strips webpack:// and ../).
Install
$ agentstack add skill-batteryshark-rekit-js-sourcemap-extract ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-batteryshark-rekit-js-sourcemap-extract) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
JS Source-Map Extractor
Recover the original source from a JavaScript source map — the fastest way to turn a minified/bundled .js back into readable files, when a map is available.
When to use
You have a minified or webpacked bundle (or a leaked prod build) and there's a source map — a .map file, or a //# sourceMappingURL= in the .js (inline data: map or a sibling .map). A map's sourcesContent usually holds the complete original source of every input file, so this beats deobfuscation: no guessing, you get the author's actual code. If there's no map, fall back to js-deobfuscate.
What it does
- Loads the map from a
.map(JSON) or from a.js'ssourceMappingURL(inline
base64 data: map, or a sibling .map file — never fetched over the network).
- Writes each
sourcesContententry tooutdir/, cleaning the path
(strips webpack://, schemes, and ../ so everything stays under the output dir).
- Reports how many sources were recovered vs. had no embedded content.
Read-only, pure stdlib. Then scan the recovered tree with js-covert-scan / js-deobfuscate.
Usage
rekit run js-sourcemap-extract ./app.min.js.map ./out
rekit run js-sourcemap-extract ./bundle.js ./out # follows its sourceMappingURLNo map found → {"hasSourceMap": false, "note": "…"}.
Prerequisites
- python3 ≥ 3.8 — pure stdlib, nothing to vendor.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/rekit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.