@rango-dev/provider-xdefi
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-transition:dist/index.js | AI (source-diff): Bundled/minified build output referencing known first-party modules, not true obfuscation. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Consistent with bundler/minifier change, not a stub swap. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): ctrl.xyz is the official Ctrl/XDEFI wallet domain; not a C2 or exfiltration endpoint. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is expected and consistent across all 300 versions. | ai |
Versions (showing 51 of 69)
| 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.0 | 6 / 0 | |
| 0.45.1 | 6 / 0 | |
| 0.45.0 | 6 / 0 | |
| 0.44.0 | 6 / 0 | |
| 0.43.0 | 6 / 0 | |
| 0.42.0 | 6 / 0 | |
| 0.41.0 | 6 / 0 | |
| 0.40.0 | 6 / 0 | |
| 0.39.0 | 6 / 0 | |
| 0.38.1 | 6 / 0 | |
| 0.38.0 | 6 / 0 | |
| 0.37.1 | 5 / 0 | |
| 0.37.0 | 5 / 0 | |
| 0.36.0 | 5 / 0 | |
| 0.35.1 | 5 / 0 | |
| 0.35.0 | 5 / 0 | |
| 0.34.0 | 5 / 0 | |
| 0.33.2 | 5 / 0 | |
| 0.33.1 | 5 / 0 | |
| 0.33.0 | 5 / 0 | |
| 0.32.1 | 5 / 0 | |
| 0.32.0 | 5 / 0 | |
| 0.31.0 | 5 / 0 | |
| 0.30.0 | 5 / 0 | |
| 0.29.0 | 5 / 0 | |
| 0.28.0 | 4 / 0 | |
| 0.27.0 | 4 / 0 | |
| 0.26.0 | 4 / 0 | |
| 0.25.0 | 4 / 0 | |
| 0.24.0 | 4 / 0 | |
| 0.23.0 | 4 / 0 | |
| 0.22.0 | 4 / 0 | |
| 0.21.0 | 4 / 0 | |
| 0.20.0 | 4 / 0 | |
| 0.19.0 | 4 / 0 |
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.