@rango-dev/wallets-core
Core package for handling web3 wallets supported by Rango
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/mod.js | AI (source-diff): Bundled esbuild output matching build script, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/legacy/mod.js | AI (source-diff): Bundled esbuild output matching build script, not true obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected from bundling new deps (zustand/immer/caip) into dist output. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a standard Proxy handler pattern; not obfuscation, stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package; missing repo/README metadata is typical for this package structure. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.60.0 | 5 / 3 | |
| 0.59.0 | 6 / 3 | |
| 0.58.1 | 5 / 1 | |
| 0.58.0 | 5 / 1 | |
| 0.57.0 | 5 / 1 | |
| 0.56.0 | 5 / 0 | |
| 0.55.0 | 4 / 0 | |
| 0.54.0 | 4 / 0 | |
| 0.51.0 | 4 / 0 | |
| 0.50.0 | 4 / 0 | |
| 0.49.0 | 4 / 0 | |
| 0.48.0 | 4 / 0 | |
| 0.47.0 | 4 / 0 | |
| 0.46.0 | 4 / 0 | |
| 0.45.0 | 4 / 0 | |
| 0.44.0 | 4 / 0 | |
| 0.43.0 | 4 / 0 | |
| 0.42.0 | 4 / 0 | |
| 0.41.0 | 4 / 0 | |
| 0.40.0 | 4 / 0 | |
| 0.39.0 | 4 / 0 | |
| 0.38.0 | 1 / 0 | |
| 0.37.0 | 2 / 0 | |
| 0.36.1 | 2 / 0 | |
| 0.36.0 | 2 / 0 | |
| 0.35.0 | 2 / 0 | |
| 0.34.0 | 2 / 0 | |
| 0.1.15 | 3 / 0 | |
| 0.1.14 | 3 / 0 | |
| 0.1.13 | 3 / 0 | |
| 0.1.12 | 3 / 0 | |
| 0.1.11 | 3 / 0 |
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.