@iconify-svelte/basil
3
Versions
CC-BY-4.0
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
cyberalien
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Icon component packages in @iconify-svelte scope routinely omit descriptions; not a malice indicator here. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher; lack of provenance is common and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@iconify/css-svelte | AI (phantom-deps): Svelte component packages reference deps in config/svelte.config rather than direct imports; stable false positive for this package type. | ai |
v1.0.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.