@abi-software/map-utilities
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@abi-software/svg-sprite | AI (phantom-deps): Same org scope (@abi-software); declared as a runtime dependency, stable false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.8.3 | 7 / 4 | |
| 1.8.2 | 7 / 4 | |
| 1.8.1 | 7 / 4 | |
| 1.8.0 | 7 / 4 | |
| 1.7.7 | 7 / 4 | |
| 1.7.6 | 7 / 4 | |
| 1.7.5 | 7 / 4 | |
| 1.7.4 | 7 / 4 | |
| 1.7.3 | 7 / 4 | |
| 1.7.2 | 7 / 4 | |
| 1.7.1 | 7 / 4 | |
| 1.7.0 | 7 / 4 | |
| 1.6.0 | 7 / 4 | |
| 1.5.0 | 7 / 4 | |
| 1.4.2 | 6 / 4 | |
| 1.4.0 | 6 / 4 | |
| 1.3.2 | 6 / 4 | |
| 1.3.1 | 6 / 4 | |
| 1.3.0 | 6 / 4 | |
| 1.2.1 | 6 / 4 | |
| 1.2.0 | 6 / 4 | |
| 1.1.2 | 5 / 4 | |
| 1.1.1 | 5 / 4 | |
| 1.1.0 | 5 / 4 | |
| 1.0.0 | 5 / 4 |
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
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.