@parcel/source-map
A source map library purpose-build for the Parcel bundler with a focus on fast combining and manipulating of source-maps.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:detect-libc | AI (phantom-deps): detect-libc removal in v2.0.4 resolves the phantom dependency; stable for this package's build pattern. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled .node binaries are the documented distribution mechanism for this native addon package; stable pattern across all versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is in build.js, a build-time script for compiling the native addon — not a runtime concern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads the correct platform-specific .node binary — canonical pattern for multi-platform native addons, not arbitrary code loading. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a well-known utility for detecting Linux C library variant, appropriate for selecting the correct native binary. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 1 / 18 | |
| 2.1.0 | 1 / 18 | |
| 2.0.5 | 1 / 18 | |
| 2.0.4 | 1 / 18 | |
| 2.0.3 | 1 / 18 | |
| 2.0.2 | 1 / 18 | |
| 2.0.1 | 0 / 18 | |
| 2.0.0 | 2 / 17 |
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.