@revealui/cli
Create RevealUI projects with a single command
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing confirmed by SLSA provenance attestation; stable pattern for this package going forward. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes with SLSA provenance; stable positive signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @clack/prompts is a well-known CLI prompts library; appropriate for a CLI tool with no malicious indicators. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @revealui/cli is a UI framework CLI tool with 107 versions and 5.7k weekly downloads; Levenshtein proximity to 'joi' is coincidental and not an impersonation attempt. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 9 / 4 | |
| 0.7.1 | 9 / 4 | |
| 0.7.0 | 9 / 4 | |
| 0.6.4 | 7 / 3 | |
| 0.6.3 | 7 / 3 | |
| 0.6.2 | 7 / 3 | |
| 0.6.1 | 7 / 3 | |
| 0.4.0 | 7 / 4 | |
| 0.3.3 | 7 / 4 | |
| 0.3.2 | 7 / 4 | |
| 0.3.1 | 7 / 4 | |
| 0.3.0 | 7 / 4 | |
| 0.2.0 | 6 / 4 |
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.