@flexpay/server
Server-side proxy helpers and Express-compatible routes for FlexPay.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @flexpay/ package; name collision with 'semver' is coincidental, not impersonation. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.1.15 | 4 / 3 | |
| 0.1.14 | 4 / 3 | |
| 0.1.13 | 4 / 3 | |
| 0.1.12 | 4 / 3 | |
| 0.1.11 | 4 / 3 | |
| 0.1.10 | 4 / 3 | |
| 0.1.9 | 4 / 3 | |
| 0.1.8 | 4 / 3 | |
| 0.1.7 | 4 / 3 | |
| 0.1.6 | 4 / 3 | |
| 0.1.5 | 4 / 3 | |
| 0.1.4 | 4 / 3 | |
| 0.1.3 | 4 / 3 | |
| 0.1.2 | 4 / 3 | |
| 0.1.0 | 4 / 3 |
v0.1.15
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage name '@flexpay/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.