@bonprix-ds/utils
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
enix79simoneggert
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Change is to GitHub Actions CI publisher, aligning with declared provenance config. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Used in config files, consistent with a styling-utils package. | ai | |
| phantom-deps | phantom-dep:tailwind-variants | AI (phantom-deps): Used in config files, consistent with a styling-utils package. | ai |
v0.1.0
2 findings
HIGH
Publisher changed: simoneggert → GitHub Actions (on unknown date)
provenance
This version was published by a different npm account than previous versions on unknown date. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
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.