@map-colonies/mc-utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with org-level automation adoption. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer ronenk added within the MapColonies org; no indicators of compromise. | ai | |
| dependencies | unvetted-dep:gdal-async | AI (dependencies): gdal-async is a legitimate GDAL binding; newly added as shapefile replacement, no malware signal. | ai | |
| dependencies | unvetted-dep:@map-colonies/types | AI (dependencies): Same-org (@map-colonies) dependency; consistent with the package's ecosystem and purpose. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 8 / 26 | |
| 6.0.0 | 8 / 26 | |
| 5.1.0 | 8 / 26 | |
| 5.0.0 | 7 / 26 | |
| 4.0.4 | 8 / 26 | |
| 3.5.6 | 8 / 24 | |
| 3.5.5 | 8 / 25 | |
| 3.5.4 | 8 / 25 | |
| 3.5.3 | 8 / 25 | |
| 3.5.2 | 8 / 25 |
v6.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.