@solvapay/react-supabase
Supabase authentication adapter for SolvaPay React Provider.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Same-org publisher transition, no compromise indicators. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): New maintainer matched by email as known prior maintainer; legitimate handoff, not compromise. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.10 | 0 / 5 | |
| 1.0.9 | 0 / 5 | |
| 1.0.8 | 0 / 5 | |
| 1.0.7 | 0 / 5 | |
| 1.0.6 | 0 / 5 | |
| 1.0.5 | 0 / 5 | |
| 1.0.4 | 0 / 5 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 |
v1.0.10
3 findingsAll previous maintainers (solvapay-admin) were replaced by new maintainers (tommy-solvapay). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tommy-solvapay) than the most recent previously approved version (solvapay-admin) on 2026-06-15, but tommy-solvapay is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tommy-solvapay) than the most recent previously approved version (solvapay-admin) on 2026-04-28, but tommy-solvapay is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.