← Home

@quenty/statestack

npm Repository Homepage
17
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

RobloxNevermoreLuaUtility

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@quenty/maid AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. ai
install-scripts install-script:preinstall AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcement pattern used across this monorepo; not malicious. ai
phantom-deps phantom-dep:@quenty/rx AI (phantom-deps): Roblox/Lua monorepo; deps may be consumed by Lua loader, not JS imports. Stable false positive for this package. ai
phantom-deps phantom-dep:@quenty/brio AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. ai
phantom-deps phantom-dep:@quenty/signal AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. ai
phantom-deps phantom-dep:@quenty/baseobject AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. ai
phantom-deps phantom-dep:@quenty/valueobject AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import. ai

Versions (showing 17 of 17)

Version Deps Published
14.31.0 7 / 0
14.30.0 7 / 0
14.24.0 7 / 0
14.23.1 7 / 0
14.23.0 7 / 0
14.22.7 7 / 0
14.22.6 7 / 0
14.22.5 7 / 0
14.22.4 7 / 0
14.22.3 7 / 0
14.22.2 7 / 0
14.22.1 7 / 0
14.22.0 7 / 0
14.21.0 6 / 0
14.20.0 6 / 0
14.19.1 6 / 0
14.19.0 6 / 0

v14.30.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.

v14.24.0

1 finding
LOW No provenance attestation provenance

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

v14.23.1

1 finding
LOW No provenance attestation provenance

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

v14.23.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.

v14.22.7

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.

v14.22.6

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.

v14.22.5

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.

v14.22.4

1 finding
LOW No provenance attestation provenance

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

v14.22.3

1 finding
LOW No provenance attestation provenance

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

v14.22.2

1 finding
LOW No provenance attestation provenance

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

v14.22.1

1 finding
LOW No provenance attestation provenance

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

v14.22.0

1 finding
LOW No provenance attestation provenance

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

v14.21.0

1 finding
LOW No provenance attestation provenance

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

v14.20.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.

v14.19.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.

v14.19.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.