← Home

@quenty/spring

Spring implementation for Roblox

17
Versions
MIT
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

RobloxNevermoreLuaSpringpid

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 is a standard monorepo package-manager enforcement; stable pattern for this package. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:@quenty/ducktype AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a false positive here. ai

Versions (showing 17 of 17)

Version Deps Published
10.12.0 2 / 0
10.9.3 2 / 0
10.9.2 2 / 0
10.9.1 2 / 0
10.9.0 2 / 0
10.8.4 2 / 0
10.8.3 2 / 0
10.8.2 2 / 0
10.8.1 2 / 0
10.8.0 2 / 0
10.7.1 2 / 0
10.7.0 2 / 0
10.6.0 2 / 0
10.5.0 2 / 0
10.4.1 2 / 0
10.4.0 2 / 0
10.3.0 2 / 0

v10.8.4

1 finding
LOW No provenance attestation provenance

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

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

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.