@uapkg/package-manifest-schema
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a runtime dependency; phantom-dep heuristic is a false positive for schema packages. | ai | |
| phantom-deps | phantom-dep:@uapkg/common-schema | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic doesn't account for re-exports. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal schema library with legitimate monorepo structure; tiny payload is expected. | ai | |
| phantom-deps | phantom-dep:@uapkg/diagnostics | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly via @uapkg/common-schema rather than directly imported. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.10 | 3 / 0 | |
| 1.1.9 | 3 / 0 | |
| 1.1.8 | 3 / 0 | |
| 1.1.7 | 3 / 0 | |
| 1.1.6 | 3 / 0 | |
| 0.1.2 | 3 / 0 | |
| 0.1.1 | 3 / 0 |
v1.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.