@revealui/services
External service integrations for RevealUI — Stripe, Supabase, and Vercel
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN ../../LICENSE.commercial | AI (license): Commercial license is appropriate for this pro package; stable pattern. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer-style dep for a React-based services package. | ai | |
| phantom-deps | phantom-dep:stripe | AI (phantom-deps): Services package likely re-exports or wraps stripe at runtime. | ai | |
| phantom-deps | phantom-dep:payload | AI (phantom-deps): CMS dependency likely used in compiled output. | ai | |
| phantom-deps | phantom-dep:@supabase/ssr | AI (phantom-deps): Supabase dep likely used in compiled output. | ai | |
| phantom-deps | phantom-dep:@supabase/supabase-js | AI (phantom-deps): Supabase dep likely used in compiled output. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): Build tool referenced in config; expected phantom-dep for this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Peer-style dep for a React-based services package. | ai | |
| phantom-deps | phantom-dep:@vitejs/plugin-react-swc | AI (phantom-deps): Vite plugin referenced in config; expected phantom-dep. | ai | |
| phantom-deps | phantom-dep:@vercel/node | AI (phantom-deps): Framework-scoped package loaded by convention in Vercel environments; analyzer itself notes this is likely a false positive. | ai | |
| dependencies | unvetted-dep:@revealui/config | AI (dependencies): First-party sibling package within the RevealUI monorepo; same GitHub org and naming convention. Not a third-party unknown dependency. | ai | |
| dependencies | unvetted-dep:@supabase/ssr | AI (dependencies): @supabase/ssr is a well-known, legitimate Supabase package; its presence in a Supabase integration library is expected and not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common (~88% of npm packages); no other indicators of supply chain compromise for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 9 / 13 | |
| 0.6.0 | 10 / 13 | |
| 0.5.0 | 10 / 13 | |
| 0.3.5 | 10 / 13 | |
| 0.3.4 | 10 / 13 | |
| 0.3.3 | 10 / 13 | |
| 0.3.2 | 10 / 13 | |
| 0.3.0 | 10 / 13 | |
| 0.2.6 | 10 / 13 | |
| 0.2.4 | 10 / 13 | |
| 0.2.2 | 10 / 13 | |
| 0.2.1 | 10 / 13 | |
| 0.2.0 | 10 / 13 | |
| 0.1.0 | 8 / 13 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 8 / 6 | |
| 0.0.1 | 8 / 6 |
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
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
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 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package 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.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.