file-type
Detect the file type of a file, stream, or data
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:is-exe | AI (dependencies): is-exe is a small sindresorhus-ecosystem utility for detecting EXE files; consistent with file-type's purpose of detecting file types from buffers. | ai | |
| dependencies | unvetted-dep:is-mp4 | AI (dependencies): is-mp4 is a small utility for detecting MP4 files; consistent with file-type's purpose and sindresorhus's ecosystem pattern. | ai | |
| dependencies | unvetted-dep:is-swf | AI (dependencies): is-swf is a small utility for detecting SWF files; consistent with file-type's purpose and sindresorhus's ecosystem pattern. | ai | |
| dependencies | unvetted-dep:audio-type | AI (dependencies): audio-type is a small utility for detecting audio file types; consistent with file-type's purpose and sindresorhus's ecosystem pattern. | ai | |
| dependencies | unvetted-dep:is-pdf | AI (dependencies): is-pdf is a semantically appropriate dependency for a file-type detection library; consistent with the package's purpose and sindresorhus ecosystem. | ai | |
| dependencies | unvetted-dep:is-epub | AI (dependencies): is-epub is a semantically appropriate dependency for a file-type detection library; consistent with the package's purpose and sindresorhus ecosystem. | ai | |
| dependencies | unvetted-dep:strtok3 | AI (dependencies): strtok3 is a well-known binary tokenizer library, a core long-standing dependency of file-type used for stream-based file parsing. Stable false positive. | ai | |
| dependencies | unvetted-dep:token-types | AI (dependencies): token-types is a companion library to strtok3 for binary token type definitions, a core long-standing dependency of file-type. Stable false positive. | ai | |
| dependencies | unvetted-dep:uint8array-extras | AI (dependencies): uint8array-extras is published by sindresorhus himself and is a legitimate utility library for Uint8Array operations used in file-type. Stable false positive. | ai | |
| dependencies | unvetted-dep:@tokenizer/inflate | AI (dependencies): @tokenizer/inflate is a decompression utility in the strtok3/tokenizer ecosystem, a legitimate core dependency for file-type's archive detection. Stable false positive. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') is a documented Webpack bundling workaround in sindresorhus/file-type; not a supply-chain risk. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus packages historically do not use Sigstore provenance; this is a stable pattern for this publisher and not a risk indicator. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 22.0.1 | 4 / 8 | |
| 22.0.0 | 4 / 7 | |
| 21.3.4 | 4 / 8 | |
| 21.3.3 | 4 / 8 | |
| 21.3.2 | 4 / 8 | |
| 12.4.2 | 0 / 7 | |
| 12.4.1 | 0 / 7 | |
| 12.4.0 | 0 / 7 | |
| 12.3.1 | 0 / 7 | |
| 12.3.0 | 0 / 7 | |
| 12.2.0 | 0 / 7 | |
| 12.1.0 | 0 / 7 | |
| 12.0.1 | 0 / 7 | |
| 12.0.0 | 0 / 7 | |
| 11.1.0 | 0 / 6 | |
| 11.0.0 | 0 / 6 | |
| 10.11.0 | 0 / 6 | |
| 10.10.0 | 0 / 6 | |
| 10.9.0 | 0 / 6 | |
| 10.8.0 | 0 / 3 | |
| 10.7.1 | 0 / 3 | |
| 10.7.0 | 0 / 3 | |
| 10.6.0 | 0 / 3 | |
| 10.5.0 | 0 / 3 | |
| 10.4.0 | 0 / 3 | |
| 10.3.0 | 0 / 3 | |
| 10.2.0 | 0 / 3 | |
| 10.1.0 | 0 / 3 | |
| 10.0.0 | 0 / 3 | |
| 9.0.0 | 0 / 3 | |
| 8.1.0 | 0 / 3 | |
| 7.7.1 | 0 / 3 | |
| 7.7.0 | 0 / 3 | |
| 7.6.0 | 0 / 3 | |
| 7.5.0 | 0 / 3 | |
| 7.4.0 | 0 / 3 | |
| 7.3.0 | 0 / 3 | |
| 7.2.0 | 0 / 3 | |
| 7.1.0 | 0 / 3 | |
| 7.0.1 | 0 / 3 | |
| 6.2.0 | 0 / 3 | |
| 6.1.0 | 0 / 3 | |
| 5.2.0 | 0 / 3 | |
| 5.1.1 | 0 / 3 | |
| 5.1.0 | 0 / 3 | |
| 5.0.0 | 0 / 3 | |
| 4.4.0 | 0 / 3 | |
| 4.3.0 | 0 / 3 | |
| 4.2.0 | 0 / 3 | |
| 4.1.0 | 0 / 3 | |
| 4.0.0 | 0 / 3 | |
| 3.9.0 | 0 / 3 | |
| 3.8.0 | 0 / 3 | |
| 3.7.0 | 0 / 3 | |
| 3.6.0 | 0 / 3 | |
| 3.5.0 | 0 / 3 | |
| 3.4.0 | 0 / 3 | |
| 3.3.1 | 0 / 3 | |
| 3.3.0 | 0 / 3 | |
| 3.2.0 | 0 / 3 | |
| 3.1.1 | 0 / 3 | |
| 3.1.0 | 0 / 3 | |
| 3.0.0 | 0 / 3 | |
| 2.12.0 | 2 / 2 | |
| 2.11.0 | 2 / 2 | |
| 2.10.2 | 2 / 1 | |
| 2.10.1 | 1 / 2 | |
| 2.10.0 | 1 / 2 | |
| 2.9.0 | 1 / 2 | |
| 2.8.0 | 1 / 2 | |
| 2.7.0 | 1 / 2 | |
| 2.6.0 | 1 / 2 | |
| 2.5.0 | 1 / 2 | |
| 2.4.0 | 1 / 2 | |
| 2.3.0 | 1 / 2 | |
| 2.2.0 | 1 / 2 | |
| 2.1.0 | 1 / 2 | |
| 2.0.3 | 1 / 2 | |
| 2.0.2 | 1 / 2 | |
| 2.0.1 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.2.0 | 10 / 2 | |
| 1.1.0 | 9 / 2 | |
| 1.0.2 | 8 / 2 | |
| 1.0.1 | 8 / 2 | |
| 1.0.0 | 8 / 2 | |
| 0.3.0 | 8 / 2 | |
| 0.2.0 | 5 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.1.0 | 3 / 2 |
v22.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
2 findingsThis version was published by a different npm account than previous versions on 2017-10-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
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.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.