← Home

@quenty/pagesutils

npm Repository Homepage

Utilities to advance over the Roblox pages API surface

10
Versions
MIT
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

quenty

Keywords

RobloxNevermoreLuaPromisePages

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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/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
phantom-deps phantom-dep:@quenty/ducktype AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua-targeting npm packages. ai

Versions (showing 10 of 10)

Version Deps Published
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

v5.19.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.18.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.13.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.13.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.13.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.13.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.