@quenty/rigbuilderutils
Utility functions for debugging, builds a Roblox character rig
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard monorepo package manager enforcement; stable pattern across all NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox Lua package; deps are declared for Lua runtime use, not JS imports. False positive for this org's packages. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same as above — Roblox Lua runtime dependency, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/assetserviceutils | AI (phantom-deps): Same as above — Roblox Lua runtime dependency, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/insertserviceutils | AI (phantom-deps): Same as above — Roblox Lua runtime dependency, not a JS import. | ai | |
| phantom-deps | phantom-dep:@quenty/humanoiddescriptionutils | AI (phantom-deps): Same as above — Roblox Lua runtime dependency, not a JS import. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 10.32.2 | 5 / 2 | |
| 10.24.1 | 5 / 2 | |
| 10.24.0 | 5 / 2 | |
| 10.23.0 | 5 / 2 | |
| 10.22.7 | 5 / 2 | |
| 10.22.6 | 5 / 2 | |
| 10.22.5 | 5 / 2 | |
| 10.22.4 | 5 / 2 | |
| 10.22.3 | 5 / 2 | |
| 10.22.2 | 5 / 2 | |
| 10.22.1 | 5 / 2 | |
| 10.22.0 | 5 / 2 | |
| 10.21.0 | 5 / 2 | |
| 10.20.2 | 5 / 2 | |
| 10.20.1 | 5 / 2 | |
| 10.20.0 | 5 / 2 | |
| 10.19.3 | 5 / 2 | |
| 10.19.2 | 5 / 2 | |
| 10.19.1 | 5 / 2 | |
| 10.19.0 | 5 / 2 | |
| 10.18.2 | 5 / 2 | |
| 10.18.1 | 5 / 2 | |
| 10.18.0 | 5 / 2 | |
| 10.17.0 | 5 / 2 | |
| 10.16.0 | 5 / 2 | |
| 10.15.0 | 5 / 2 | |
| 10.14.0 | 5 / 2 | |
| 10.13.1 | 5 / 2 | |
| 10.13.0 | 5 / 2 | |
| 10.12.0 | 5 / 2 | |
| 10.11.1 | 5 / 2 | |
| 10.11.0 | 5 / 2 | |
| 10.10.1 | 5 / 2 | |
| 10.10.0 | 5 / 2 | |
| 10.9.0 | 5 / 2 | |
| 10.8.0 | 5 / 2 | |
| 10.7.0 | 5 / 2 | |
| 10.6.0 | 5 / 2 | |
| 10.5.0 | 5 / 2 | |
| 10.4.0 | 5 / 2 |
v10.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.