@quenty/elo
Elo rating utility library.
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard package manager enforcement pattern used across this monorepo. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @quenty/elo package from established NevermoreEngine monorepo; no impersonation of glob. | ai | |
| phantom-deps | phantom-dep:@quenty/probability | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for Lua/Roblox packages. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Test framework dep referenced in config, not imported directly; expected pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org monorepo test runner dep; phantom-dep heuristic unreliable for this package type. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.35.2 | 3 / 3 | |
| 7.25.1 | 1 / 3 | |
| 7.25.0 | 1 / 3 | |
| 7.24.1 | 1 / 3 | |
| 7.24.0 | 1 / 3 | |
| 7.23.7 | 1 / 3 | |
| 7.23.6 | 1 / 3 | |
| 7.23.5 | 1 / 3 | |
| 7.23.4 | 1 / 3 | |
| 7.23.3 | 1 / 3 | |
| 7.23.2 | 1 / 3 | |
| 7.23.1 | 1 / 3 | |
| 7.23.0 | 1 / 3 | |
| 7.22.0 | 1 / 3 | |
| 7.21.0 | 1 / 3 | |
| 7.20.1 | 1 / 3 | |
| 7.20.0 | 1 / 3 |
v7.35.2
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.1
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.