@rango-dev/provider-coin98
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/mod.js | AI (source-diff): Standard bundled build output with readable imports; not obfuscated. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is consistent across all @rango-dev/* packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across @rango-dev monorepo packages; not indicative of malice. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.62.0 | 7 / 0 | |
| 0.61.1 | 7 / 0 | |
| 0.61.0 | 7 / 0 | |
| 0.60.0 | 7 / 0 | |
| 0.59.0 | 7 / 0 | |
| 0.58.0 | 7 / 0 | |
| 0.57.0 | 7 / 0 | |
| 0.56.1 | 7 / 0 | |
| 0.54.0 | 7 / 0 | |
| 0.53.0 | 7 / 0 | |
| 0.52.0 | 7 / 0 | |
| 0.51.0 | 7 / 0 | |
| 0.50.0 | 6 / 0 | |
| 0.49.0 | 6 / 0 | |
| 0.48.0 | 6 / 0 | |
| 0.47.0 | 6 / 0 | |
| 0.46.1 | 6 / 0 | |
| 0.46.0 | 6 / 0 |
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.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.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.