← Home

@quenty/insertserviceutils

npm Repository Homepage

InsertServiceUtils to make loading models via insert service easy

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

RobloxNevermoreLua

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Part of large Roblox/NevermoreEngine monorepo; batch releases after gaps are normal for this publisher. ai
install-scripts install-script:preinstall AI (install-scripts): Standard only-allow pnpm enforcer; stable pattern across all NevermoreEngine monorepo packages. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:@quenty/promise AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a false positive here. ai

Versions (showing 10 of 10)

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

1 finding
LOW No provenance attestation provenance

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

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.5

1 finding
LOW No provenance attestation provenance

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

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.