@ripple-ts/cli
Interactive CLI tool for creating Ripple applications
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @ripple-ts/cli is a CLI scaffold tool, not a typosquat of joi; Levenshtein match is coincidental. | ai |
Versions (showing 15 of 126)
| Version | Deps | Published |
|---|---|---|
| 0.2.172 | 0 / 11 | |
| 0.2.171 | 0 / 11 | |
| 0.2.170 | 0 / 11 | |
| 0.2.169 | 0 / 11 | |
| 0.2.167 | 0 / 11 | |
| 0.2.164 | 0 / 11 | |
| 0.2.163 | 0 / 11 | |
| 0.2.162 | 0 / 11 | |
| 0.2.161 | 0 / 11 | |
| 0.2.160 | 0 / 11 | |
| 0.2.158 | 0 / 11 | |
| 0.2.156 | 0 / 11 | |
| 0.2.155 | 0 / 11 | |
| 0.2.154 | 0 / 11 | |
| 0.2.153 | 0 / 11 |
v0.2.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.