@awesome.me/webawesome
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:@konnorr/qr-creator | AI (dependencies): Scoped fork of qr-creator by the same maintainer (konnor_rogers); intentional internal replacement of the unscoped dep. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.10.0 | 13 / 9 | |
| 3.9.0 | 13 / 9 | |
| 3.8.0 | 12 / 8 | |
| 3.7.0 | 10 / 8 | |
| 3.6.0 | 10 / 8 | |
| 3.5.0 | 10 / 8 | |
| 3.4.0 | 9 / 8 | |
| 3.3.1 | 9 / 8 | |
| 3.2.1 | 9 / 7 | |
| 3.2.0 | 9 / 7 | |
| 3.1.0 | 9 / 4 |
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.