@rango-dev/provider-safe
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is a known pattern for @rango-dev scoped packages, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @rango-dev monorepo sub-package publishing pattern. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.53.0 | 7 / 0 | |
| 0.52.1 | 7 / 0 | |
| 0.52.0 | 7 / 0 | |
| 0.51.0 | 7 / 0 | |
| 0.50.0 | 7 / 0 | |
| 0.49.0 | 7 / 0 | |
| 0.48.0 | 7 / 0 | |
| 0.47.1 | 7 / 0 | |
| 0.45.0 | 7 / 0 | |
| 0.44.0 | 7 / 0 | |
| 0.43.0 | 7 / 0 | |
| 0.42.0 | 7 / 0 | |
| 0.41.0 | 6 / 0 | |
| 0.40.0 | 6 / 0 | |
| 0.39.0 | 6 / 0 | |
| 0.38.0 | 6 / 0 | |
| 0.37.1 | 6 / 0 | |
| 0.37.0 | 6 / 0 |
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.