Welcome to the central submission hub for the Sourcemaps Archive Team. This repository is dedicated to tracking, triaging, and managing the preservation of frontend source maps.
Our goal is to preserve the "human-readable" history of the web. By archiving sourcemaps, we ensure that even as websites evolve or disappear, the original logic, comments, and structure of their frontend code remain accessible for educational and research purposes.
To suggest a website or specific JavaScript bundle for archiving, please follow these steps:
- Navigate to the [Issues] tab of this repository.
- Click New Issue.
- Select the Archive Request template.
- Fill out the website URL and any specific details (such as whether the maps are public or if the site is facing an imminent shutdown).
Important
Security first: Please do not post private API keys, user credentials, or sensitive internal environment variables in public issues.
Once a request is submitted, our team follows a standard workflow:
- Triage: We verify if the
sourceMappingURLis active and if the maps are reachable. - Archiving: The maps are pulled and stored in our Private Archive or Public Archive depending on the project's nature.
- Verification: We ensure the unminified code is reconstructed correctly.
- Closure: The issue is labeled
status: archivedonce the process is complete.
We use labels to keep our workflow organized:
| Label | Description |
|---|---|
priority: high |
Sites at risk of being taken down or major updates pending. |
type: private |
Sourcemaps that will only be stored in our internal, non-public vault. |
status: archived |
Successfully processed and stored. |
needs-investigation |
The URL was provided, but the maps are hidden or require special headers. |
| “Bridging the gap between production bundles and original source code.” |
Would you like me to add a "Tools We Use" section to this README to highlight any specific software or scripts your team utilizes for the extraction?