← Home

@quenty/tuple

npm Repository Homepage

Tuple utility package

13
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

RobloxNevermoreLuatuple

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; stable pattern across this monorepo's packages. 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/lrucache AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a false positive here. ai

Versions (showing 13 of 13)

Version Deps Published
1.8.0 2 / 0
1.6.2 2 / 0
1.6.1 2 / 0
1.6.0 2 / 0
1.5.3 2 / 0
1.5.2 2 / 0
1.5.1 2 / 0
1.5.0 2 / 0
1.4.1 2 / 0
1.4.0 2 / 0
1.3.0 2 / 0
1.2.0 2 / 0
1.1.0 2 / 0

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

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

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