← Home

@tus/server

npm Repository Homepage
5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

acconuttus-botmurderlonuppydev

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; established package with strong ecosystem trust mitigates takeover concern. ai
maintainer-change maintainer-added AI (maintainer-change): uppydev is the Uppy/tus org account; addition is expected for this monorepo. ai
phantom-deps phantom-dep:set-cookie-parser AI (phantom-deps): set-cookie-parser is a declared runtime dep; phantom-dep heuristic is a false positive here. ai
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped package @tus/server is unrelated to semver; Levenshtein match is coincidental. ai

Versions (showing 5 of 5)

Version Deps Published
2.4.1 5 / 12
2.4.0 5 / 12
2.3.0 5 / 12
2.2.1 5 / 12
1.0.0 1 / 15

v2.4.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.0

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

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.0

2 findings
HIGH Publisher changed: murderlon → uppydev (on 2025-07-30) provenance

This version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

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

Package name '@tus/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.