formdata-node
Spec-compliant FormData implementation for Node.js
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:octetstream.me | AI (email-domain): Long-standing maintainer's personal domain; npm identity is established via npm credentials, not email DNS. 184 approved packages, 3946 days on npm. | ai | |
| provenance | missing-githead | AI (provenance): Maintainer switched to changesets-based release workflow; missing gitHead reflects CI tooling change, not a supply-chain compromise signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with clean history; lack of Sigstore provenance is a process gap, not a security indicator for this package. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 0 / 25 | |
| 6.0.2 | 0 / 25 | |
| 6.0.1 | 0 / 25 | |
| 6.0.0 | 0 / 25 | |
| 5.0.1 | 2 / 20 | |
| 5.0.0 | 2 / 19 | |
| 4.4.1 | 2 / 21 | |
| 4.4.0 | 2 / 21 | |
| 4.3.3 | 2 / 22 | |
| 4.3.2 | 2 / 21 | |
| 4.3.1 | 2 / 22 | |
| 4.3.0 | 2 / 22 | |
| 4.2.4 | 2 / 22 | |
| 4.2.3 | 2 / 22 | |
| 4.2.2 | 2 / 22 | |
| 4.2.1 | 2 / 22 | |
| 4.2.0 | 2 / 22 | |
| 4.1.0 | 2 / 22 | |
| 4.0.1 | 2 / 22 | |
| 4.0.0 | 2 / 22 | |
| 3.7.0 | 3 / 22 | |
| 3.6.4 | 3 / 22 | |
| 3.6.3 | 3 / 21 | |
| 3.6.2 | 3 / 23 | |
| 3.6.1 | 3 / 23 | |
| 3.6.0 | 3 / 23 | |
| 3.5.4 | 3 / 25 | |
| 3.5.3 | 3 / 25 | |
| 3.5.2 | 3 / 25 | |
| 3.5.1 | 3 / 25 | |
| 3.5.0 | 3 / 25 | |
| 3.4.0 | 3 / 25 | |
| 3.3.2 | 3 / 25 | |
| 3.3.1 | 3 / 25 | |
| 3.3.0 | 3 / 25 | |
| 3.2.0 | 3 / 27 | |
| 3.1.1 | 3 / 27 | |
| 3.1.0 | 3 / 26 | |
| 3.0.0 | 3 / 26 | |
| 2.5.0 | 1 / 19 | |
| 2.4.0 | 1 / 18 | |
| 2.3.0 | 1 / 18 | |
| 2.2.2 | 2 / 26 | |
| 2.2.1 | 2 / 26 | |
| 2.2.0 | 2 / 26 | |
| 2.1.4 | 3 / 25 | |
| 2.1.3 | 3 / 25 | |
| 2.1.2 | 3 / 25 | |
| 2.1.1 | 3 / 25 | |
| 2.1.0 | 3 / 25 | |
| 2.0.1 | 3 / 25 |
v6.0.2
3 findingsMaintainer email '[email protected]' uses domain 'octetstream.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octetstream.
v6.0.1
3 findingsMaintainer email '[email protected]' uses domain 'octetstream.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octetstream.
v6.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octetstream.
Maintainer email '[email protected]' uses domain 'octetstream.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.