← Home

@tekir/bodyparser

npm Repository Homepage

Multipart form and file upload parsing middleware

5
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

tekirio

Keywords

tekirbuntypescriptframeworknodejsfullstack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Fired on a comment describing path traversal mitigation, not actual /etc/passwd access. Stable false positive for this package. ai
typosquat typosquat.levenshtein:body-parser AI (typosquat): Scoped @tekir package in its own framework monorepo; name similarity to body-parser is incidental, not impersonation. ai
typosquat typosquat.pattern:body-parser AI (typosquat): Same rationale: @tekir namespace clearly distinguishes this from body-parser; pattern match is a false positive. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.4 2 / 0
0.1.3 2 / 0
0.1.2 2 / 0
0.1.1 2 / 0
0.1.0 2 / 0

v0.1.4

2 findings
HIGH etc-passwd-access: src/parser.ts:97 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 95 | // Strip any path separators a user-supplied `tmpFileName()` might 96 | // return so a malicious or buggy hook can't write outside `tmpDir` > 97 | // (`../../etc/passwd`, absolute paths, etc.). We then double-check 98 | // the resolved final path stays under `tmpDirAbs`. 99 | const raw = config?.tmpFileName ? config.tmpFileName() : `${crypto.randomUUID()}.${uploaded.extname}`

LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

3 findings
HIGH typosquat.levenshtein: Possible typosquat of 'body-parser' typosquat

Package name '@tekir/bodyparser' is 1 edit(s) away from popular package 'body-parser'.

HIGH typosquat.pattern: Suspicious name similarity to 'body-parser' typosquat

Package name '@tekir/bodyparser' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'body-parser'.

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.