@nextrush/multipart
Streaming multipart/form-data parser and file upload middleware for NextRush
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Fires only in test code validating that path traversal via /etc/passwd is stripped — correct security behavior, not credential harvesting. | ai |
v3.0.5
4 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 141 | 142 | it('strips path components (unix)', () => { > 143 | expect(sanitizeFilename('/etc/passwd')).toBe('passwd'); 144 | }); 145 |
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 421 | const storage = new DiskStorage({ 422 | dest: tmpDir, > 423 | filename: () => '../../../etc/passwd', 424 | }); 425 | const stream = uint8ArrayToReadableStream(encoder.encode('traversal'));
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 529 | it('sanitizes filenames', async () => { 530 | const body = createMultipartBody([ > 531 | { name: 'file', filename: '../../../etc/passwd', type: 'text/plain', content: 'evil' }, 532 | ]); 533 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.