@gulp-sourcemaps/identity-map
Gulp plugin for generating an identity sourcemap for a file.
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): nmccready is a long-standing npm publisher (136 approved packages, first seen 3481 days ago) within the gulp-sourcemaps org; transition from phated appears legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a no-material-change patch release from a trusted publisher in the gulp-sourcemaps org; no evidence of takeover. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 5 / 8 | |
| 2.0.0 | 5 / 8 | |
| 1.0.2 | 5 / 10 | |
| 1.0.1 | 5 / 10 | |
| 1.0.0 | 5 / 10 |
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2020-03-09. 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.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.