@quenty/optional
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package manager enforcement script; stable pattern for this monorepo package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 11.11.0 | 1 / 0 | |
| 11.9.2 | 1 / 0 | |
| 11.9.1 | 1 / 0 | |
| 11.9.0 | 1 / 0 | |
| 11.8.3 | 1 / 0 | |
| 11.8.2 | 1 / 0 | |
| 11.8.1 | 1 / 0 | |
| 11.8.0 | 1 / 0 | |
| 11.7.1 | 1 / 0 | |
| 11.7.0 | 1 / 0 | |
| 11.6.0 | 1 / 0 | |
| 11.5.0 | 1 / 0 | |
| 11.4.0 | 1 / 0 | |
| 11.3.0 | 1 / 0 |
v11.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.