@quenty/pagesutils
Utilities to advance over the Roblox pages API surface
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:@quentystudios/jest-lua | AI (phantom-deps): Test tooling dep in Lua monorepo; not import-scannable, same pattern as other org deps. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org test dep, consistent with existing accepted phantom deps in this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo; individual sub-packages can go dormant between bulk releases without indicating takeover. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm enforcer; stable pattern across this monorepo's packages. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua-targeting npm packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua-targeting npm packages. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua-targeting npm packages. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 5.22.0 | 5 / 0 | |
| 5.20.0 | 3 / 0 | |
| 5.19.1 | 3 / 0 | |
| 5.19.0 | 3 / 0 | |
| 5.18.0 | 3 / 0 | |
| 5.14.0 | 3 / 0 | |
| 5.13.4 | 3 / 0 | |
| 5.13.3 | 3 / 0 | |
| 5.13.2 | 3 / 0 | |
| 5.13.1 | 3 / 0 | |
| 5.13.0 | 3 / 0 | |
| 5.12.0 | 3 / 0 | |
| 5.11.4 | 3 / 0 | |
| 5.11.3 | 3 / 0 | |
| 5.11.2 | 3 / 0 | |
| 5.11.1 | 3 / 0 | |
| 5.11.0 | 3 / 0 | |
| 5.10.0 | 3 / 0 | |
| 5.9.0 | 3 / 0 | |
| 5.8.0 | 2 / 0 | |
| 5.7.1 | 2 / 0 | |
| 5.7.0 | 2 / 0 | |
| 5.6.0 | 2 / 0 | |
| 5.5.0 | 2 / 0 | |
| 5.4.0 | 2 / 0 | |
| 5.3.0 | 2 / 0 | |
| 5.2.0 | 2 / 0 | |
| 5.1.0 | 2 / 0 | |
| 5.0.0 | 2 / 0 |
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.