@quenty/signal
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Large monorepo package; irregular publish cadence is expected and publisher has strong track record. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package-manager enforcement; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org dependency in a Roblox/Lua package; likely used at runtime in Lua, not via Node imports. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 7.13.1 | 1 / 0 | |
| 7.13.0 | 1 / 0 | |
| 7.12.0 | 1 / 0 | |
| 7.11.5 | 1 / 0 | |
| 7.11.4 | 1 / 0 | |
| 7.11.3 | 1 / 0 | |
| 7.11.2 | 1 / 0 | |
| 7.11.1 | 1 / 0 | |
| 7.11.0 | 1 / 0 |
v7.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.