@revealui/ai
[Pro] AI system for RevealUI - memory, LLM, orchestration, and tools
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 | slsa-provenance | AI (provenance): Package consistently publishes with SLSA provenance attestation via GitHub Actions CI/CD — strong supply chain integrity signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual publish (revealui-org) to GitHub Actions CI/CD is a legitimate and security-improving workflow change, corroborated by SLSA attestation. | ai | |
| license | uncommon-license:SEE LICENSE IN ../../LICENSE.commercial | AI (license): RevealUI is a commercial product; this license reference is consistent across all versions and reflects intentional commercial licensing, not a red flag. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @revealui/ai; Levenshtein match to 'joi' is a false positive — entirely different namespace, purpose, and branding. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @revealui/ai; Levenshtein match to 'ajv' is a false positive — entirely different namespace, purpose, and branding. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @revealui/ai is a branded AI framework; Levenshtein match to 'hapi' is a false positive with no plausible typosquat scenario. | ai | |
| dependencies | unvetted-dep:@revealui/core | AI (dependencies): First-party sibling package within the @revealui monorepo; expected internal dependency, not a third-party supply chain risk. | ai | |
| dependencies | unvetted-dep:@revealui/db | AI (dependencies): First-party sibling package within the @revealui monorepo; expected internal dependency, not a third-party supply chain risk. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @revealui/ai; Levenshtein match to 'pg' is a false positive — entirely different namespace, purpose, and branding. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @revealui/ai; Levenshtein match to 'qs' is a false positive — entirely different namespace, purpose, and branding. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 6 / 9 | |
| 0.5.0 | 6 / 9 | |
| 0.4.0 | 6 / 9 | |
| 0.3.0 | 5 / 8 | |
| 0.2.9 | 5 / 8 | |
| 0.2.8 | 5 / 8 | |
| 0.2.7 | 5 / 8 | |
| 0.2.6 | 5 / 8 | |
| 0.2.5 | 5 / 8 | |
| 0.2.4 | 5 / 8 | |
| 0.2.2 | 5 / 9 | |
| 0.2.0 | 5 / 9 | |
| 0.1.3 | 5 / 9 | |
| 0.1.2 | 5 / 9 | |
| 0.1.1 | 5 / 9 | |
| 0.1.0 | 4 / 10 |
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v0.4.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This 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.2.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This 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.2.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: revealui-org.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: revealui-org.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.