@revealui/db
Drizzle ORM schema and dual-database client (NeonDB + Supabase) 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 publishes via GitHub Actions CI/CD with SLSA attestation; publisher-changed to GHA is expected and verified. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Package is a growing DB schema/query library; new files correspond directly to new schema and query exports documented in package.json exports map. Pattern is expected for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @revealui/db is not a typosquat of 'pg'; it's a database layer for the RevealUI monorepo. Levenshtein match is a false positive for scoped names. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @revealui/db is not a typosquat of 'qs'; it's a database layer for the RevealUI monorepo. Levenshtein match is a false positive for scoped names. | ai | |
| dependencies | unvetted-dep:@revealui/utils | AI (dependencies): Sibling monorepo package within the @revealui namespace; risk is tied to the RevealUI ecosystem, not an independent third-party dependency. | ai | |
| dependencies | unvetted-dep:@revealui/config | AI (dependencies): Sibling monorepo package within the @revealui namespace; risk is tied to the RevealUI ecosystem, not an independent third-party dependency. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 6 / 5 | |
| 0.6.0 | 6 / 5 | |
| 0.5.0 | 6 / 5 | |
| 0.4.0 | 6 / 5 | |
| 0.3.7 | 6 / 5 | |
| 0.3.6 | 6 / 5 | |
| 0.3.5 | 5 / 6 | |
| 0.3.4 | 5 / 6 | |
| 0.3.3 | 5 / 6 | |
| 0.3.1 | 5 / 6 | |
| 0.3.0 | 7 / 4 | |
| 0.2.1 | 7 / 4 | |
| 0.2.0 | 7 / 4 |
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
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.5.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.4.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.