← Home

@quenty/memoize

npm Repository Homepage
17
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

RobloxNevermoreLuamemoize

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Part of NevermoreEngine monorepo with 1116 approved packages; batch releases after gaps are normal for this publisher. ai
install-scripts install-script:preinstall AI (install-scripts): only-allow pnpm is a benign package-manager enforcement script; stable pattern for this monorepo. ai
phantom-deps phantom-dep:@quenty/tuple AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. ai
phantom-deps phantom-dep:@quenty/lrucache AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. ai
phantom-deps phantom-dep:@quenty/typeutils AI (phantom-deps): Same-org monorepo dep; indirect import pattern is expected. ai

Versions (showing 17 of 17)

Version Deps Published
1.9.1 4 / 0
1.9.0 4 / 0
1.8.0 4 / 0
1.7.3 4 / 0
1.7.2 4 / 0
1.7.1 4 / 0
1.7.0 3 / 0
1.6.3 3 / 0
1.6.2 3 / 0
1.6.1 3 / 0
1.6.0 3 / 0
1.5.1 3 / 0
1.5.0 3 / 0
1.4.0 3 / 0
1.3.0 3 / 0
1.2.0 3 / 0
1.1.0 2 / 0

v1.6.3

1 finding
LOW No provenance attestation provenance

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

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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.