@rango-dev/provider-slush
Slush integration for hub. [Homepage](https://slush.app/) | [Docs](https://docs.sui.io/standards/wallet-standard)
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Part of @rango-dev monorepo; 64 versions published; no material changes from prior version; dormancy consistent with infrequent wallet provider updates. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo wallet provider package; sparse metadata is consistent across the @rango-dev ecosystem. | ai | |
| phantom-deps | phantom-dep:@mysten/sui | AI (phantom-deps): @mysten/sui is declared as a direct dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 6 / 0 | |
| 0.15.1 | 6 / 0 | |
| 0.15.0 | 6 / 0 | |
| 0.14.0 | 6 / 0 | |
| 0.13.0 | 6 / 0 | |
| 0.12.0 | 6 / 0 | |
| 0.11.0 | 6 / 0 | |
| 0.10.1 | 6 / 0 | |
| 0.8.0 | 6 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.6.0 | 6 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.4.0 | 5 / 0 | |
| 0.3.0 | 5 / 0 | |
| 0.2.0 | 5 / 0 | |
| 0.1.0 | 5 / 0 |
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.