@rango-dev/ui
Rango UI components
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @rango-dev package; not a typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @rango-dev package; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @rango-dev package; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @rango-dev package; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @rango-dev package; not a typosquat of yup. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.64.0 | 12 / 14 | |
| 0.63.0 | 12 / 14 | |
| 0.62.1 | 12 / 14 | |
| 0.62.0 | 12 / 14 | |
| 0.61.0 | 12 / 14 | |
| 0.60.0 | 12 / 14 | |
| 0.59.0 | 12 / 14 | |
| 0.58.0 | 12 / 14 | |
| 0.57.1 | 12 / 14 | |
| 0.55.0 | 12 / 14 | |
| 0.46.1 | 12 / 14 | |
| 0.46.0 | 12 / 14 | |
| 0.45.0 | 12 / 14 | |
| 0.44.0 | 12 / 14 | |
| 0.43.0 | 12 / 14 | |
| 0.42.0 | 12 / 14 | |
| 0.41.0 | 12 / 14 | |
| 0.40.0 | 12 / 14 | |
| 0.39.0 | 12 / 14 | |
| 0.38.0 | 13 / 14 | |
| 0.37.0 | 13 / 14 | |
| 0.36.1 | 13 / 14 | |
| 0.36.0 | 13 / 14 | |
| 0.35.0 | 13 / 14 | |
| 0.34.0 | 13 / 14 | |
| 0.33.0 | 13 / 22 | |
| 0.32.0 | 13 / 22 |
v0.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.1
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.