← Home

@quenty/marketplaceutils

npm Repository Homepage
36
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

quenty

Keywords

RobloxNevermoreLuaMarketplaceServicePromises

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Same-org test-tooling deps from trusted long-standing publisher. ai
phantom-deps phantom-dep:@quentystudios/jest-lua AI (phantom-deps): Lua source, not JS-importable; test dep from trusted same-author scope. ai
phantom-deps phantom-dep:@quenty/playermock AI (phantom-deps): Same-org test dep, Lua source not scanned by JS import heuristic. ai
phantom-deps phantom-dep:@quenty/nevermore-test-runner AI (phantom-deps): Same-org test dep, Lua source not scanned by JS import heuristic. ai
dependencies unvetted-dep:@quenty/playermock AI (dependencies): Same publisher/org, long-established ecosystem. ai
dependencies unvetted-dep:@quentystudios/jest-lua AI (dependencies): Test-lua fork maintained by same author group. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Roblox/Lua package; deps declared for tooling, not JS imports. Stable false positive. ai
phantom-deps phantom-dep:@quenty/memoize AI (phantom-deps): Same as above — Lua package dep pattern, not a JS import. ai
phantom-deps phantom-dep:@quenty/promise AI (phantom-deps): Same as above — Lua package dep pattern, not a JS import. ai
phantom-deps phantom-dep:@quenty/servicebag AI (phantom-deps): Same as above — Lua package dep pattern, not a JS import. ai
install-scripts install-script:preinstall AI (install-scripts): only-allow pnpm enforcer; stable pattern across all NevermoreEngine packages. ai

Versions (showing 36 of 36)

Version Deps Published
11.25.1 7 / 0
11.25.0 7 / 0
11.24.0 4 / 0
11.23.0 4 / 0
11.22.0 4 / 0
11.21.0 4 / 0
11.20.1 4 / 0
11.20.0 4 / 0
11.19.0 4 / 0
11.17.0 4 / 0
11.16.0 4 / 0
11.15.0 4 / 0
11.14.0 4 / 0
11.13.6 4 / 0
11.13.5 4 / 0
11.13.4 4 / 0
11.13.3 4 / 0
11.13.2 3 / 0
11.13.1 3 / 0
11.13.0 3 / 0
11.12.1 3 / 0
11.12.0 3 / 0
11.11.4 3 / 0
11.11.3 3 / 0
11.11.2 3 / 0
11.11.1 3 / 0
11.11.0 3 / 0
11.10.0 3 / 0
11.9.0 3 / 0
11.8.1 3 / 0
11.8.0 3 / 0
11.7.0 3 / 0
11.6.0 3 / 0
11.5.0 3 / 0
11.4.0 3 / 0
11.3.0 2 / 0

v11.25.1

1 finding
LOW No provenance attestation provenance

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

v11.25.0

1 finding
LOW No provenance attestation provenance

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

v11.24.0

1 finding
LOW No provenance attestation provenance

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

v11.23.0

1 finding
LOW No provenance attestation provenance

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

v11.22.0

1 finding
LOW No provenance attestation provenance

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

v11.21.0

1 finding
LOW No provenance attestation provenance

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

v11.20.0

1 finding
LOW No provenance attestation provenance

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

v11.17.0

1 finding
LOW No provenance attestation provenance

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

v11.16.0

1 finding
LOW No provenance attestation provenance

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

v11.15.0

1 finding
LOW No provenance attestation provenance

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

v11.14.0

1 finding
LOW No provenance attestation provenance

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

v11.13.6

1 finding
LOW No provenance attestation provenance

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

v11.13.5

1 finding
LOW No provenance attestation provenance

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

v11.11.4

1 finding
LOW No provenance attestation provenance

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

v11.11.3

1 finding
LOW No provenance attestation provenance

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

v11.11.2

1 finding
LOW No provenance attestation provenance

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

v11.11.1

1 finding
LOW No provenance attestation provenance

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

v11.11.0

1 finding
LOW No provenance attestation provenance

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

v11.10.0

1 finding
LOW No provenance attestation provenance

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

v11.9.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.

v11.8.1

1 finding
LOW No provenance attestation provenance

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

v11.8.0

1 finding
LOW No provenance attestation provenance

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

v11.7.0

1 finding
LOW No provenance attestation provenance

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

v11.6.0

1 finding
LOW No provenance attestation provenance

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

v11.5.0

1 finding
LOW No provenance attestation provenance

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

v11.4.0

1 finding
LOW No provenance attestation provenance

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

v11.3.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.