@quenty/humanoidspeed
Handles humanoid speed in a centralized location
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 monorepo package manager enforcement; stable across all NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Roblox/Lua package; deps are not JS imports, phantom-dep heuristic is a stable false positive for this org. | ai | |
| phantom-deps | phantom-dep:@quenty/binder | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/characterutils | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/rogue-humanoid | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/playerhumanoidbinder | AI (phantom-deps): Same as above — Roblox/Lua package, not JS imports. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 12.48.0 | 9 / 0 | |
| 12.46.2 | 9 / 0 | |
| 12.35.0 | 9 / 0 | |
| 12.34.0 | 9 / 0 | |
| 12.33.1 | 9 / 0 | |
| 12.33.0 | 9 / 0 | |
| 12.32.7 | 9 / 0 | |
| 12.32.6 | 9 / 0 | |
| 12.32.5 | 7 / 0 | |
| 12.32.4 | 7 / 0 | |
| 12.32.3 | 7 / 0 | |
| 12.32.2 | 7 / 0 | |
| 12.32.1 | 7 / 0 | |
| 12.32.0 | 7 / 0 | |
| 12.31.1 | 7 / 0 | |
| 12.31.0 | 7 / 0 | |
| 12.30.0 | 7 / 0 | |
| 12.29.0 | 7 / 0 | |
| 12.28.0 | 7 / 0 | |
| 12.27.1 | 7 / 0 | |
| 12.27.0 | 7 / 0 | |
| 12.26.2 | 7 / 0 | |
| 12.26.1 | 7 / 0 | |
| 12.26.0 | 7 / 0 | |
| 12.25.0 | 7 / 0 | |
| 12.24.0 | 7 / 0 |
v12.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.46.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.
v12.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.32.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.32.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.