← Home

@walletconnect/crypto

npm Repository Homepage

Isomorphic Cryptography Library for AES, HMAC and SHA2

5
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

pedrouidmagizizbkremnachosandevcelinegancho_walletconnectcyberdrkzorukalukaisailovicenesozturkchris13524huxwell

Keywords

cryptocryptographyisomorphicaeshmacsha2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed-stale AI (provenance): Historic 2022 maintainer transfer, long-stable on npm, not a takeover indicator. ai
maintainer-change maintainer-added AI (maintainer-change): Reflects the same long-settled team transition, not a new anomaly. ai
publish-pattern new-deps-added AI (publish-pattern): tslib is a standard, benign TypeScript helper library. ai
typosquat typosquat.levenshtein:bcrypt AI (typosquat): Scoped WalletConnect crypto utility; Levenshtein match to bcrypt is coincidental, not impersonation. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.0 6 / 12
1.0.3 6 / 15
1.0.2 5 / 16
1.0.1 5 / 16
1.0.0 5 / 16

v1.0.3

2 findings
MEDIUM Publisher changed: pedrouid → bkrem (on 2022-11-25, unremoved on npm for 1339d) provenance

This version was published by a different npm account (bkrem) than the most recent previously approved version (pedrouid) on 2022-11-25. It has since remained available on npm for 1339 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

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