← Home

@passkeys/core

npm Homepage
3
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mosesbotfboucquezdevopsrobotismamzheadfirediegomuraandrejbandrewtoth-exodusolisticjanwefarisissamerlzr4vnryanzimbulgakovkfrankliexoduschalker633kh4cktenaciousmvmarkoexodusmarcos.kichelakinncarfederico-pomariosvladjoshua-rogers-exodussergii_bokevvanantoaquiguillecuranachoalvarezcoreycollinsxogdgsripwoudharshjv

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped wallet utility package; name collision with 'cors' is purely coincidental, not impersonation. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is standard for Solana/Bitcoin key and signature handling in this crypto wallet library. ai

Versions (showing 3 of 3)

Version Deps Published
4.1.0 3 / 0
4.0.1 3 / 0
4.0.0 3 / 0

v4.1.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@passkeys/core' is 1 edit(s) away from popular package 'cors'.

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.

v4.0.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@passkeys/core' is 1 edit(s) away from popular package 'cors'.

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.

v4.0.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@passkeys/core' is 1 edit(s) away from popular package 'cors'.

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.