@solvapay/server
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): Intra-org publisher transition, stable across versions. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Provenance analyzer confirms new publisher matched by email to existing maintainer, not a hijack. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known maintainer transition, corroborated by provenance record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Prior maintainer replaced by known co-maintainer, not suspicious removal. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): @solvapay/server is a scoped payment SDK package; similarity to 'semver' is coincidental string overlap, not impersonation. The @solvapay monorepo context makes this a stable false positive. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 11 | |
| 1.3.0 | 1 / 11 | |
| 1.2.1 | 1 / 11 | |
| 1.2.0 | 1 / 11 | |
| 1.1.1 | 1 / 11 | |
| 1.1.0 | 1 / 11 | |
| 1.0.12 | 1 / 11 | |
| 1.0.11 | 1 / 11 | |
| 1.0.10 | 1 / 11 | |
| 1.0.9 | 1 / 11 | |
| 1.0.8 | 1 / 11 | |
| 1.0.7 | 1 / 10 | |
| 1.0.6 | 1 / 10 | |
| 1.0.5 | 1 / 10 | |
| 1.0.4 | 1 / 10 | |
| 1.0.3 | 1 / 10 | |
| 1.0.2 | 1 / 10 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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-07-01, 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.1.0
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-05-13, 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.12
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-05-05, 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.