@realfavicongenerator/gulp-real-favicon
Generate a multiplatform favicon with RealFaviconGenerator and Gulp
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:@realfavicongenerator/inject-markups | AI (dependencies): First-party scoped dep from the same @realfavicongenerator org; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of provenance is a process gap, not a security signal. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-json | AI (phantom-deps): @rollup/plugin-json is a build-time rollup plugin loaded by convention in rollup.config.mjs, not directly imported in source. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 7 / 9 | |
| 0.8.0 | 7 / 9 | |
| 0.6.3 | 7 / 9 | |
| 0.6.0 | 7 / 9 | |
| 0.5.0 | 7 / 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
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.