fd
File descriptor manager
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): 'fd' is a natural abbreviation for 'file descriptor', not a typosquat of 'pg'. Short names will always have low edit distances to other short names. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): 'fd' is a natural abbreviation for 'file descriptor', not a typosquat of 'qs'. Mechanical Levenshtein match on short names is a false positive here. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): 'fd' is a natural abbreviation for 'file descriptor', not a typosquat of 'zod'. Mechanical Levenshtein match on short names is a false positive here. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 13+ years old with 249k weekly downloads. Version 0.0.0 was the author's initial release convention, not a malicious throwaway. | ai |
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.