combine-source-map
Add source maps of multiple files, offset them and then combine them into one source map
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): thlorenz is the original author (repo URL and author field both reference thlorenz); the publisher change from zertosh is a legitimate maintainer transition, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature 13-year-old utility package; long gaps between releases are normal. No material code changes introduced in this version. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 4 / 1 | |
| 0.7.2 | 4 / 1 | |
| 0.7.1 | 4 / 1 | |
| 0.7.0 | 4 / 1 | |
| 0.6.1 | 4 / 1 | |
| 0.5.0 | 3 / 1 | |
| 0.4.0 | 3 / 1 | |
| 0.3.0 | 3 / 1 | |
| 0.2.0 | 3 / 1 | |
| 0.1.3 | 3 / 1 | |
| 0.1.2 | 3 / 1 | |
| 0.1.1 | 3 / 1 | |
| 0.1.0 | 3 / 1 |
v0.8.0
2 findingsThis version was published by a different npm account than previous versions on 2017-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.