@map-colonies/mc-priority-queue
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Org-published package with SLSA provenance; dormancy likely reflects project cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org library; sparse README and no keywords are consistent across all versions, not spam indicators. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 9.1.2 | 1 / 22 | |
| 9.1.1 | 1 / 22 | |
| 9.1.0 | 1 / 22 | |
| 9.0.2 | 0 / 22 | |
| 9.0.0 | 0 / 22 |
v9.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.