@fncts/query
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore-attested CI/CD provenance. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Part of the @fncts org monorepo; consistently missing description across versions, not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package pattern; sparse metadata is structural, not indicative of spam/malware. | ai | |
| phantom-deps | phantom-dep:@fncts/typelevel | AI (phantom-deps): Same-scope monorepo dep; likely used transitively or at type-level only. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.27 | 3 / 0 | |
| 0.0.26 | 3 / 0 | |
| 0.0.25 | 3 / 0 | |
| 0.0.24 | 3 / 0 |
v0.0.27
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.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.