@web-widget/lifecycle-cache
End-to-end lifecycle caching
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of a large monorepo; sparse README and no keywords are typical for internal scoped packages. | ai |
Versions (showing 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 1 / 9 | |
| 1.15.0 | 1 / 9 | |
| 1.14.1 | 1 / 9 | |
| 1.14.0 | 1 / 9 | |
| 1.13.0 | 1 / 9 | |
| 1.12.0 | 1 / 9 | |
| 1.11.0 | 1 / 9 |
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.