@quenty/grouputils
Group utility functions for Roblox
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Lua source, not JS import-scannable; expected false positive. | ai | |
| dependencies | unvetted-dep:@quenty/playermock | AI (dependencies): Same-org test mock package, part of Nevermore monorepo tooling. | ai | |
| dependencies | unvetted-dep:@quentystudios/jest-lua | AI (dependencies): Test framework dep from affiliated org, used for Lua testing. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Lua source, not JS import-scannable; expected false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/playermock | AI (phantom-deps): Lua source, not JS import-scannable; expected false positive. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 887 approved packages with 0 rejections; dormancy likely reflects upstream Roblox project cadence, not account takeover. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive here. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard monorepo package-manager enforcement; stable for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 10.23.0 | 5 / 0 | |
| 10.20.2 | 2 / 0 | |
| 10.19.0 | 2 / 0 | |
| 10.18.0 | 2 / 0 | |
| 10.17.0 | 2 / 0 | |
| 10.16.0 | 2 / 0 | |
| 10.13.0 | 2 / 0 | |
| 10.12.6 | 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 | |
| 10.11.0 | 2 / 0 | |
| 10.10.4 | 2 / 0 | |
| 10.10.3 | 2 / 0 | |
| 10.10.2 | 2 / 0 | |
| 10.10.1 | 2 / 0 | |
| 10.10.0 | 2 / 0 | |
| 10.9.0 | 2 / 0 | |
| 10.8.0 | 2 / 0 | |
| 10.7.1 | 2 / 0 | |
| 10.7.0 | 2 / 0 | |
| 10.6.0 | 2 / 0 | |
| 10.5.0 | 2 / 0 | |
| 10.4.0 | 2 / 0 | |
| 10.3.0 | 2 / 0 | |
| 10.2.0 | 2 / 0 | |
| 10.1.0 | 2 / 0 | |
| 10.0.0 | 2 / 0 |
v10.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.2
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.