@fncts/http
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 benign when CI/CD attestation confirms build integrity. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package in @fncts org scope; missing description is a style issue, not a risk indicator. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:find-my-way | AI (phantom-deps): find-my-way is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fncts/typelevel | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.0.13 | 8 / 0 | |
| 0.0.12 | 8 / 0 | |
| 0.0.11 | 8 / 0 | |
| 0.0.10 | 8 / 0 | |
| 0.0.9 | 8 / 0 | |
| 0.0.8 | 8 / 0 | |
| 0.0.7 | 8 / 0 | |
| 0.0.6 | 8 / 0 | |
| 0.0.5 | 8 / 0 | |
| 0.0.4 | 8 / 0 | |
| 0.0.3 | 8 / 0 | |
| 0.0.2 | 8 / 0 | |
| 0.0.1 | 8 / 0 |
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.