@emdash-cms/registry-client
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Legitimate monorepo package from established publisher; 0.0.0 reflects initial release convention, not malicious intent. | ai | |
| phantom-deps | phantom-dep:@atcute/atproto | AI (phantom-deps): Declared as a runtime dep; phantom-dep heuristic fires because it's not directly imported in analyzed files, but it's a legitimate peer/transitive dep for this atproto client package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 4 / 8 | |
| 0.3.0 | 5 / 7 | |
| 0.2.0 | 4 / 6 | |
| 0.1.0 | 4 / 6 | |
| 0.0.1 | 4 / 6 | |
| 0.0.0 | 4 / 6 |
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.