@quenty/enumutils
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Part of large monorepo with consistent publisher history; inactivity gap is not suspicious given context. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard package manager enforcement script; stable pattern for this monorepo package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.4.6 | 0 / 0 | |
| 3.4.5 | 0 / 0 | |
| 3.4.4 | 0 / 0 | |
| 3.4.3 | 0 / 0 | |
| 3.4.2 | 0 / 0 | |
| 3.4.1 | 0 / 0 | |
| 3.4.0 | 0 / 0 | |
| 3.3.0 | 0 / 0 | |
| 3.2.0 | 0 / 0 | |
| 3.1.0 | 0 / 0 | |
| 3.0.0 | 0 / 0 |
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
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.0
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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.