← Home

@web3auth/no-modal

Multi chain wallet aggregator for web3Auth

17
Versions
ISC
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

chaitanyapottiarchit_web3himanshunpm009

Keywords

web3Auth/no-modalweb3AuthmultichainWalletblockchainethereumsolana

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:bignumber.js AI (phantom-deps): bignumber.js is a direct runtime dep in package.json; phantom-dep false positive for this package. ai
phantom-deps phantom-dep:bowser AI (phantom-deps): Declared in deps for bundler use; stable false positive for this package. ai
phantom-deps phantom-dep:jsonschema AI (phantom-deps): Declared in deps for bundler use; stable false positive for this package. ai
phantom-deps phantom-dep:assert AI (phantom-deps): Declared in deps for bundler polyfill; stable false positive for this package. ai
phantom-deps phantom-dep:@toruslabs/eccrypto AI (phantom-deps): First-party toruslabs dep declared for bundler; stable false positive. ai
phantom-deps phantom-dep:@toruslabs/tweetnacl-js AI (phantom-deps): First-party toruslabs dep declared for bundler; stable false positive. ai
phantom-deps phantom-dep:permissionless AI (phantom-deps): Declared in deps for bundler use; stable false positive for this package. ai

Versions (showing 17 of 17)

Version Deps Published
11.0.1 32 / 12
11.0.0 32 / 12
10.16.0 37 / 10
10.15.0 37 / 10
10.13.0 37 / 10
10.11.0 37 / 10
10.8.1 37 / 10
10.8.0 37 / 10
10.5.6 37 / 10
10.5.3 37 / 10
10.5.1 37 / 10
10.5.0 37 / 10
10.4.0 37 / 10
10.3.1 37 / 10
10.3.0 37 / 10
10.2.0 37 / 10
10.0.1 37 / 10

v11.0.1

1 finding
LOW No provenance attestation provenance

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

v11.0.0

1 finding
LOW No provenance attestation provenance

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

v10.16.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.

v10.13.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.

v10.11.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.

v10.8.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.

v10.8.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.

v10.5.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.

v10.5.3

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.

v10.5.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.

v10.5.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.

v10.4.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.

v10.3.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.

v10.3.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.

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

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