@revealui/sync
ElectricSQL sync utilities for RevealUI
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): Package uses GitHub Actions CI/CD publishing with SLSA attestation; this transition is the expected automated publisher pattern for this org. | ai | |
| dependencies | unvetted-dep:lib0 | AI (dependencies): lib0 is the core utility library for Yjs, a standard dependency for any Yjs-based sync package. Its presence is expected and legitimate for this package's purpose. | ai | |
| dependencies | unvetted-dep:@electric-sql/react | AI (dependencies): @electric-sql/react is the official React bindings for ElectricSQL, directly aligned with this package's stated purpose of ElectricSQL sync utilities. | ai | |
| typosquat | typosquat.levenshtein:async | AI (typosquat): Scoped package @revealui/sync is not impersonating 'async'; the Levenshtein match is a false positive due to the scoped namespace. Package purpose and metadata are coherent with the RevealUI org. | ai | |
| phantom-deps | phantom-dep:@revealui/contracts | AI (phantom-deps): Same-org scoped dependency; phantom detection in monorepo packages is expected when deps are used transitively or re-exported. | ai | |
| phantom-deps | phantom-dep:@revealui/db | AI (phantom-deps): Same-org scoped dependency; phantom detection in monorepo packages is expected when deps are used transitively or re-exported. | ai | |
| phantom-deps | phantom-dep:@revealui/cache | AI (phantom-deps): Same-org scoped dependency; phantom detection in monorepo packages is expected when deps are used transitively or re-exported. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.10 | 8 / 10 | |
| 0.3.9 | 8 / 10 | |
| 0.3.8 | 8 / 10 | |
| 0.3.7 | 8 / 10 | |
| 0.3.6 | 7 / 10 | |
| 0.3.5 | 7 / 10 | |
| 0.3.4 | 7 / 10 | |
| 0.3.3 | 7 / 10 | |
| 0.3.1 | 7 / 11 | |
| 0.3.0 | 7 / 11 | |
| 0.2.1 | 7 / 11 | |
| 0.2.0 | 7 / 11 |
v0.3.10
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. 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.9
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.8
2 findingsPackage name '@revealui/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.