@fncts/typelevel
9
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
0x706b
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 cosmetic given CI/CD publish chain. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Typelevel utility package in a monorepo; no description/keywords/deps is expected for this type of package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.25 | 0 / 0 | |
| 0.0.24 | 0 / 0 | |
| 0.0.23 | 0 / 0 | |
| 0.0.22 | 0 / 0 | |
| 0.0.21 | 0 / 0 | |
| 0.0.20 | 0 / 0 | |
| 0.0.19 | 0 / 0 | |
| 0.0.18 | 0 / 0 | |
| 0.0.17 | 0 / 0 |
v0.0.21
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.