@jjlmoya/utils-creative
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:astro | AI (phantom-deps): Astro is used via config/CLI, not direct imports; stable for this Astro-based package. | ai | |
| phantom-deps | phantom-dep:astro-icon | AI (phantom-deps): Astro plugin referenced in config, not direct imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@iconify-json/mdi | AI (phantom-deps): Icon JSON pack consumed by astro-icon plugin, not direct imports. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 4 / 15 | |
| 1.6.0 | 4 / 15 | |
| 1.5.0 | 4 / 15 | |
| 1.4.0 | 4 / 15 | |
| 1.3.0 | 4 / 15 | |
| 1.2.0 | 4 / 15 |
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.