@realfavicongenerator/grunt-real-favicon
Generate a multiplatform favicon with RealFaviconGenerator and Grunt
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/grunt | AI (dependencies): Type definitions package; no runtime risk, stable false positive for this grunt plugin. | ai | |
| dependencies | unvetted-dep:@realfavicongenerator/inject-markups | AI (dependencies): Same-namespace sibling package from the same monorepo; expected dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/grunt | AI (phantom-deps): @types/grunt is a TypeScript type declaration; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-json | AI (phantom-deps): Rollup plugin loaded via rollup.config.mjs by convention, not direct import in source. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 5 / 9 | |
| 0.8.0 | 5 / 9 | |
| 0.6.3 | 5 / 9 | |
| 0.6.0 | 5 / 9 | |
| 0.5.1 | 5 / 9 | |
| 0.5.0 | 5 / 9 |
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.