← Home

@0xsequence/wallet-core

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

Maintainers

naivesheeppkieltykaagusx1211taylanpincemilkytaste

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped monorepo package; missing metadata is a known pattern for @0xsequence sub-packages, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent across @0xsequence monorepo packages; not indicative of malice. ai
provenance no-provenance AI (provenance): No provenance across the @0xsequence monorepo; stable false positive for this package family. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Standard Proxy/Reflect passthrough in debug wrapper; not obfuscation. ai
phantom-deps phantom-dep:mipd AI (phantom-deps): Peer/config-referenced dep in a monorepo; stable false positive. ai
phantom-deps phantom-dep:viem AI (phantom-deps): Peer/config-referenced dep in a monorepo; stable false positive. ai

Versions (showing 12 of 12)

Version Deps Published
3.0.11 6 / 8
3.0.10 6 / 8
3.0.9 6 / 8
3.0.8 6 / 8
3.0.7 6 / 8
3.0.6 6 / 8
3.0.5 6 / 8
3.0.4 6 / 8
3.0.3 6 / 8
3.0.2 6 / 8
3.0.1 6 / 8
3.0.0 6 / 8

v3.0.11

1 finding
LOW No provenance attestation provenance

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

v3.0.10

1 finding
LOW No provenance attestation provenance

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

v3.0.9

1 finding
LOW No provenance attestation provenance

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

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

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.

v3.0.6

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.

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

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.

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

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

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