@quenty/playersservicepromises
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 with 235 versions; bulk re-releases after gaps are expected, not indicative of takeover. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package-manager enforcement pattern; stable across all NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 10.18.0 | 2 / 0 | |
| 10.15.0 | 2 / 0 | |
| 10.14.0 | 2 / 0 | |
| 10.12.5 | 2 / 0 | |
| 10.12.4 | 2 / 0 | |
| 10.12.3 | 2 / 0 | |
| 10.12.2 | 2 / 0 | |
| 10.12.1 | 2 / 0 | |
| 10.12.0 | 2 / 0 |
v10.18.0
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.
v10.15.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.14.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.5
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.