@cabloy/extend
17
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
zhennann
Keywords
cabloyframework
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 Cabloy framework monorepo; mass-production and sparse metadata are expected for this publisher's packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.2.8 | 0 / 2 | |
| 3.2.5 | 0 / 0 | |
| 3.2.4 | 0 / 0 | |
| 3.2.3 | 0 / 2 | |
| 3.2.2 | 0 / 2 | |
| 3.2.1 | 0 / 2 | |
| 3.1.13 | 0 / 0 | |
| 3.1.12 | 0 / 0 | |
| 3.1.11 | 0 / 0 | |
| 3.1.10 | 0 / 0 | |
| 3.1.9 | 0 / 0 | |
| 3.1.8 | 0 / 0 | |
| 3.1.6 | 0 / 0 | |
| 3.1.3 | 0 / 2 | |
| 3.1.2 | 0 / 2 | |
| 3.0.12 | 0 / 0 | |
| 3.0.9 | 0 / 0 |
v3.0.12
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
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.