← Home

@quenty/jsonutils

8
Versions
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

RobloxNevermoreLuaJSON

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement pattern used across NevermoreEngine monorepo packages. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua tooling dependencies. ai
phantom-deps phantom-dep:@quenty/promise AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua tooling dependencies. ai

Versions (showing 8 of 8)

Version Deps Published
10.18.0 2 / 0
10.17.0 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

v10.17.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.

v10.12.4

1 finding
LOW No provenance attestation provenance

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

v10.12.3

1 finding
LOW No provenance attestation provenance

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

v10.12.2

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.

v10.12.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.

v10.12.0

1 finding
LOW No provenance attestation provenance

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

v10.11.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.