← Home

@quenty/cubicspline

18
Versions
License
No
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

RobloxNevermoreLuasplinecubic-spline

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Large monorepo with irregular release cadence; publisher has strong track record and package metadata is consistent. 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 Roblox/Lua package; phantom-dep heuristic unreliable for Lua runtime deps. ai
phantom-deps phantom-dep:@quenty/binarysearch AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua runtime deps. ai
phantom-deps phantom-dep:@quenty/linearsystemssolver AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua runtime deps. ai

Versions (showing 18 of 18)

Version Deps Published
10.12.1 3 / 0
10.12.0 3 / 0
10.11.0 3 / 0
10.10.0 3 / 0
10.9.3 3 / 0
10.9.2 3 / 0
10.9.1 3 / 0
10.9.0 3 / 0
10.8.3 3 / 0
10.8.2 3 / 0
10.8.1 3 / 0
10.8.0 3 / 0
10.7.1 3 / 0
10.7.0 3 / 0
10.6.0 3 / 0
10.5.0 3 / 0
10.4.0 3 / 0
10.3.0 3 / 0

v10.8.3

1 finding
LOW No provenance attestation provenance

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

v10.8.2

1 finding
LOW No provenance attestation provenance

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

v10.8.1

1 finding
LOW No provenance attestation provenance

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

v10.8.0

1 finding
LOW No provenance attestation provenance

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

v10.7.1

1 finding
LOW No provenance attestation provenance

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

v10.7.0

1 finding
LOW No provenance attestation provenance

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

v10.6.0

1 finding
LOW No provenance attestation provenance

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

v10.5.0

1 finding
LOW No provenance attestation provenance

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

v10.4.0

1 finding
LOW No provenance attestation provenance

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

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