@realfavicongenerator/generate-logo
Generate a logo
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@realfavicongenerator/image-adapter-node | AI (phantom-deps): Same-org scoped dep declared in dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.8.4 | 4 / 6 | |
| 0.8.3 | 4 / 6 | |
| 0.8.0 | 4 / 6 | |
| 0.6.3 | 4 / 6 | |
| 0.6.0 | 4 / 6 | |
| 0.5.0 | 4 / 6 | |
| 0.4.16 | 4 / 6 | |
| 0.4.15 | 4 / 6 | |
| 0.4.14 | 4 / 6 | |
| 0.4.13 | 4 / 6 |
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.