@revealui/setup
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 publisher is backed by SLSA provenance attestation; consistent with org-level CI/CD adoption. | ai | |
| provenance | no-provenance | AI (provenance): RevealUI monorepo packages consistently lack Sigstore provenance; this is a stable characteristic of the publisher, not a per-version anomaly. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is declared as a runtime dep and referenced in config files; not directly imported in analyzed code but legitimately part of this CLI package's dependency graph. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): ora is a declared runtime dependency in a setup utility package; phantom detection likely due to indirect usage or config-file references in compiled output. | ai | |
| phantom-deps | phantom-dep:@revealui/config | AI (phantom-deps): Same-org monorepo dependency; expected to be used indirectly or via re-exports in this setup package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency; phantom detection likely due to indirect usage in validators or config files not directly traced by the analyzer. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): execa is a declared runtime dependency in a setup/CLI utility; phantom detection likely due to indirect usage patterns not traced by the analyzer. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 5 / 5 | |
| 0.3.6 | 5 / 5 | |
| 0.3.5 | 5 / 5 | |
| 0.3.4 | 5 / 5 | |
| 0.3.3 | 5 / 5 | |
| 0.3.2 | 5 / 5 | |
| 0.3.1 | 5 / 5 | |
| 0.3.0 | 5 / 5 | |
| 0.2.0 | 6 / 5 |
v0.4.0
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.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.