@fncts/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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of the @fncts monorepo; sparse metadata and empty CJS entry are consistent with the package's structure across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all versions of this package; not indicative of malice. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.25 | 2 / 0 | |
| 0.0.24 | 2 / 0 | |
| 0.0.23 | 2 / 0 | |
| 0.0.22 | 2 / 0 |
v0.0.25
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 0x706b.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.