s3rver
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
jamhallleontastickherock
Keywords
fakes3servermockfalseamazon
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): s3rver is the canonical name for this S3 mock server, not a typo of semver. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for S3 continuation token parsing — legitimate protocol implementation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode used for Windows filesystem path encoding — legitimate platform compatibility code. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 11 / 21 |
v3.7.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.