@mearie/codegen
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): Monorepo package; 0.0.0 is the coordinated version across all @mearie/* packages, not a throwaway. | ai | |
| phantom-deps | phantom-dep:@mearie/config | AI (phantom-deps): Same-org monorepo dep; likely used transitively or via re-export, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@mearie/shared | AI (phantom-deps): Same-org monorepo dep; likely used transitively or via re-export, not a real phantom. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 7 / 6 | |
| 0.1.6 | 7 / 6 | |
| 0.1.5 | 7 / 6 | |
| 0.1.4 | 7 / 6 | |
| 0.1.3 | 7 / 6 | |
| 0.1.2 | 7 / 6 | |
| 0.0.0 | 6 / 3 |
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
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.