@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, so a manually published version cannot be tied back to a reviewed commit.
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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.8.4 | 5 / 9 | |
| 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 | |
| 0.4.16 | 5 / 9 | |
| 0.4.12 | 5 / 9 | |
| 0.4.9 | 5 / 9 | |
| 0.4.6 | 5 / 9 | |
| 0.4.4 | 5 / 9 | |
| 0.4.3 | 5 / 9 | |
| 0.4.2 | 5 / 9 | |
| 0.4.1 | 5 / 9 | |
| 0.4.0 | 5 / 9 | |
| 0.3.3 | 5 / 9 | |
| 0.3.2 | 5 / 9 | |
| 0.3.1 | 5 / 9 |
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.