← Home

@rcompat/crypto

npm Repository

Standard library cryptographic functions

22
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

terrablue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:bcrypt AI (typosquat): Scoped monorepo package @rcompat/crypto; name similarity to bcrypt is coincidental, not impersonation. ai
phantom-deps phantom-dep:@rcompat/assert AI (phantom-deps): Same-org dependency; likely used transitively or in type-only context within the monorepo. ai

Versions (showing 22 of 22)

Version Deps Published
0.22.0 1 / 1
0.21.0 1 / 1
0.20.0 1 / 1
0.19.0 1 / 1
0.18.0 1 / 1
0.17.0 1 / 1
0.16.1 1 / 1
0.16.0 1 / 1
0.15.0 1 / 1
0.14.0 1 / 1
0.13.0 1 / 1
0.12.0 1 / 0
0.11.0 0 / 0
0.10.0 0 / 0
0.9.0 0 / 0
0.8.1 0 / 0
0.8.0 0 / 0
0.7.0 0 / 0
0.6.0 0 / 0
0.5.0 0 / 0
0.4.0 0 / 0
0.2.0 0 / 0

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

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