← Home

@rango-dev/wallets-react

npm

React package for handling web3 wallets supported by Rango

48
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

yeager-eren

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): ts-results is a well-known, small utility lib; benign addition. ai
source-diff obfuscated-file:dist/helpers/index.js AI (source-diff): Bundled esbuild/tsup output with accompanying sourcemap, not true obfuscation. ai
dependencies unvetted-dep:@hub3js/evm AI (dependencies): Internal org dependency from same monorepo refactor, not third-party. ai
dependencies unvetted-dep:@hub3js/std AI (dependencies): Internal org dependency from same monorepo refactor, not third-party. ai
dependencies unvetted-dep:@hub3js/namespaces AI (dependencies): Internal org dependency from same monorepo refactor, not third-party. ai
dependencies unvetted-dep:@hub3js/solana AI (dependencies): Internal org dependency from same monorepo refactor, not third-party. ai
dependencies unvetted-dep:@hub3js/core AI (dependencies): Internal org dependency from same monorepo refactor, not third-party. ai
bogus-package bogus-package AI (bogus-package): Sub-package helper entry point; sparse metadata is structural, not spam. ai

Versions (showing 48 of 48)

Version Deps Published
0.47.0 11 / 3
0.46.0 4 / 4
0.45.1 4 / 3
0.45.0 4 / 3
0.44.0 4 / 3
0.43.0 4 / 3
0.42.0 4 / 2
0.41.0 4 / 2
0.40.1 4 / 2
0.38.0 4 / 2
0.37.0 4 / 2
0.36.0 4 / 2
0.35.0 4 / 2
0.34.0 4 / 2
0.33.0 4 / 2
0.32.0 4 / 2
0.31.0 4 / 2
0.30.1 4 / 2
0.30.0 4 / 2
0.29.0 4 / 2
0.28.0 4 / 2
0.27.0 3 / 0
0.26.0 3 / 0
0.25.0 3 / 0
0.24.0 3 / 0
0.23.0 3 / 0
0.22.0 3 / 0
0.21.1 3 / 0
0.21.0 3 / 0
0.20.0 3 / 0
0.19.0 3 / 0
0.18.0 3 / 0
0.17.0 3 / 0
0.16.0 3 / 0
0.15.0 3 / 0
0.14.0 3 / 0
0.13.0 3 / 0
0.12.0 3 / 0
0.11.0 3 / 0
0.10.0 3 / 0
0.9.0 3 / 0
0.8.0 3 / 0
0.7.0 3 / 0
0.6.0 3 / 0
0.5.0 3 / 0
0.4.0 3 / 0
0.3.0 3 / 0
0.2.0 3 / 0

v0.47.0

1 finding
LOW No provenance attestation provenance

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

v0.29.0

2 findings
HIGH New obfuscated file: dist/helpers/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.28.0

2 findings
HIGH New obfuscated file: dist/helpers/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.27.0

1 finding
LOW No provenance attestation provenance

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

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.0

1 finding
LOW No provenance attestation provenance

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

v0.24.0

1 finding
LOW No provenance attestation provenance

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

v0.23.0

1 finding
LOW No provenance attestation provenance

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

v0.22.0

1 finding
LOW No provenance attestation provenance

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

v0.21.1

1 finding
LOW No provenance attestation provenance

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

v0.21.0

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

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

v0.18.0

1 finding
LOW No provenance attestation provenance

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

v0.17.0

1 finding
LOW No provenance attestation provenance

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

v0.16.0

1 finding
LOW No provenance attestation provenance

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

v0.15.0

1 finding
LOW No provenance attestation provenance

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

v0.14.0

1 finding
LOW No provenance attestation provenance

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

v0.13.0

1 finding
LOW No provenance attestation provenance

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

v0.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

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