@rango-dev/provider-all
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@rango-dev/provider-vultisig | AI (dependencies): First-party @rango-dev namespace dep; consistent with this package's role as an all-providers aggregator. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-freighter | AI (dependencies): First-party @rango-dev namespace dep; consistent with this package's role as an all-providers aggregator. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-clover | AI (dependencies): Same-org sibling package in rango-dev monorepo; consistent pattern across all provider-all versions. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-argentx | AI (dependencies): Same-org sibling package in rango-dev monorepo; consistent pattern across all provider-all versions. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-mytonwallet | AI (dependencies): Same-org sibling package in rango-dev monorepo; consistent pattern across all provider-all versions. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-solflare-snap | AI (dependencies): Same-org sibling package in rango-dev monorepo; consistent pattern across all provider-all versions. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-halo | AI (dependencies): Same @rango-dev org; provider-all is an aggregator of rango providers, unvetted siblings are expected. | ai | |
| dependencies | unvetted-dep:@rango-dev/provider-frontier | AI (dependencies): Same @rango-dev org; consistent with aggregator role across all rango wallet providers. | ai | |
| provenance | no-provenance | AI (provenance): Rango-dev monorepo consistently publishes without provenance; stable pattern across 383 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal aggregator package; missing description is consistent across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo umbrella package; sparse metadata is structural, not a spam/malware indicator. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.62.1 | 40 / 0 | |
| 0.62.0 | 40 / 0 | |
| 0.61.1 | 38 / 0 | |
| 0.61.0 | 38 / 0 | |
| 0.60.0 | 39 / 0 | |
| 0.59.0 | 38 / 0 | |
| 0.58.0 | 38 / 0 | |
| 0.57.0 | 39 / 0 | |
| 0.56.1 | 38 / 0 | |
| 0.54.0 | 38 / 0 | |
| 0.53.0 | 38 / 0 | |
| 0.51.0 | 38 / 0 | |
| 0.50.0 | 37 / 0 | |
| 0.49.0 | 37 / 0 | |
| 0.48.0 | 37 / 0 | |
| 0.47.0 | 36 / 0 | |
| 0.46.0 | 37 / 0 | |
| 0.45.1 | 37 / 0 | |
| 0.45.0 | 37 / 0 |
v0.62.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.