← Home

@quenty/ellipticcurvecryptography

11
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

RobloxNevermoreLuaellipticcurvecryptography

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcement pattern; stable for this monorepo package. ai
phantom-deps phantom-dep:@quentystudios/jest-lua AI (phantom-deps): Test runner dep referenced in config files only; not imported at runtime. Stable false positive for this package. ai
phantom-deps phantom-dep:@quenty/nevermore-test-runner AI (phantom-deps): Test runner from same org scope; config-only reference, not a runtime import. Stable false positive. ai

Versions (showing 11 of 11)

Version Deps Published
1.12.0 2 / 0
1.11.0 2 / 0
1.7.2 0 / 0
1.7.1 0 / 0
1.7.0 0 / 0
1.6.2 0 / 0
1.6.1 0 / 0
1.6.0 0 / 0
1.5.0 0 / 0
1.4.0 0 / 0
1.3.0 0 / 0

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

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