@bcc-code/icons-vue
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
karsten.kueppernbogdanit.accountsadelinnlaurensgroeneveldu12206050jakubc-projects
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions via OIDC trusted publisher — expected for CI/CD automated publishing. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation confirms legitimate CI/CD origin from bcc-code org. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library with 31k files; large file count is expected for a Vue icon component package. | ai |
v1.5.0
2 findings
HIGH
Publisher changed: it.accounts → GitHub Actions (on 2026-05-21)
provenance
This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
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.