← Home

@quenty/qframe

npm Repository Homepage

CFrame representation as a quaternion for Roblox

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

Maintainers

quenty

Keywords

RobloxNevermoreLuacframequaternions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): only-allow pnpm enforcer; benign package-manager guard used across NevermoreEngine monorepo packages. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org Roblox/Lua tooling dependency; phantom-dep heuristic unreliable for Lua-targeted packages. ai

Versions (showing 27 of 27)

Version Deps Published
10.28.0 1 / 3
10.20.2 1 / 3
10.20.1 1 / 3
10.20.0 1 / 3
10.19.0 1 / 3
10.17.0 1 / 3
10.14.0 1 / 3
10.12.5 1 / 3
10.12.4 1 / 3
10.12.3 1 / 3
10.12.2 1 / 3
10.12.1 1 / 3
10.12.0 1 / 3
10.11.0 1 / 3
10.10.4 1 / 3
10.10.3 1 / 3
10.10.2 1 / 3
10.10.1 1 / 3
10.10.0 1 / 3
10.9.0 1 / 3
10.8.0 1 / 3
10.7.1 1 / 3
10.7.0 1 / 3
10.6.0 1 / 3
10.5.0 1 / 3
10.4.0 1 / 3
10.3.0 1 / 3

v10.28.0

1 finding
LOW No provenance attestation provenance

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

v10.10.4

1 finding
LOW No provenance attestation provenance

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

v10.10.3

1 finding
LOW No provenance attestation provenance

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

v10.10.2

1 finding
LOW No provenance attestation provenance

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

v10.10.1

1 finding
LOW No provenance attestation provenance

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

v10.10.0

1 finding
LOW No provenance attestation provenance

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

v10.9.0

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.