← Home

@better-s3/server

npm Repository Homepage

Framework-agnostic S3 server handlers — presigned uploads, downloads, deletes, and multipart operations

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

hamidrezakz

Keywords

s3serverpresigned-urluploaddownloadmultipartframework-agnostic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): hamidrezakz confirmed as known maintainer by email match on prior approved versions; not a hostile takeover. ai
maintainer-change maintainer-added AI (maintainer-change): New publisher was already a known maintainer; stable false positive for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of houk is consistent with a legitimate maintainer transition, not a takeover. ai
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped S3 utility package; name similarity to semver is coincidental, not impersonation. ai
phantom-deps phantom-dep:@aws-sdk/s3-presigned-post AI (phantom-deps): Framework-scoped AWS SDK package; loaded by convention as noted in the finding. ai
phantom-deps phantom-dep:@aws-sdk/s3-request-presigner AI (phantom-deps): Framework-scoped AWS SDK package; loaded by convention as noted in the finding. ai

Versions (showing 18 of 18)

Version Deps Published
3.1047.0 2 / 4
3.1046.0 2 / 4
3.1045.2 2 / 4
3.1045.1 2 / 4
3.1045.0 2 / 4
3.1044.0 2 / 4
3.3.0 2 / 5
3.2.1 2 / 5
3.2.0 2 / 5
3.1.1 2 / 5
3.1.0 2 / 5
3.0.0 2 / 5
2.3.1 1 / 4
2.3.0 1 / 4
2.2.0 1 / 4
2.1.0 1 / 4
2.0.0 1 / 4
1.0.0 2 / 4

v3.1047.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (houk) were replaced by new maintainers (hamidrezakz). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: houk → hamidrezakz (on 2026-05-30, known maintainer) provenance

This version was published by a different npm account (hamidrezakz) than the most recent previously approved version (houk) on 2026-05-30, but hamidrezakz 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.

v3.1046.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1045.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1045.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1045.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1044.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@better-s3/server' is 1 edit(s) away from popular package 'semver'.

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.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

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.

v1.0.0

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.