@parcel/fs MIT 50 versions

@parcel/fs

npm Repository Homepage

Blazing fast, zero configuration web application bundler

50

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

devongovett

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:qs	AI (typosquat): @parcel/fs is a legitimate scoped package in the official Parcel bundler org; Levenshtein match to 'qs' is purely coincidental and not a typosquat.	ai	2026/04/24
typosquat	typosquat.levenshtein:pg	AI (typosquat): @parcel/fs is a legitimate scoped package in the official Parcel bundler org; Levenshtein match to 'pg' is purely coincidental and not a typosquat.	ai	2026/04/24
phantom-deps	phantom-dep:utility-types	AI (phantom-deps): utility-types is a declared runtime dep used in TypeScript type definitions; its absence from direct JS imports is expected for type-only usage.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in @parcel/fs is used for loading platform-specific native modules within the Parcel monorepo — a stable, intentional pattern not representing arbitrary code execution risk.	ai	2026/04/24

Versions (showing 50 of 50)

Show 19 prereleases

Version	Deps	Published
2.16.4	6 / 5	2026-02-02
2.16.3	6 / 5	2025-12-06
2.16.2	6 / 5	2025-12-06
2.16.1	6 / 5	2025-11-05
2.16.0	6 / 5	2025-09-18
2.15.4	6 / 5	2025-06-20
2.15.3	6 / 5	2025-06-20
2.15.2	6 / 5	2025-05-25
2.15.1	6 / 5	2025-05-16
2.15.0	6 / 5	2025-05-12
2.14.4	6 / 5	2025-03-29
2.14.3	6 / 5	2025-03-29
2.14.2	6 / 5	2025-03-23
2.14.1	6 / 5	2025-03-19
2.14.0	6 / 5	2025-03-18
2.13.3	6 / 5	2024-12-16
2.13.2	6 / 5	2024-11-25
2.13.1	6 / 5	2024-11-25
2.13.0	6 / 5	2024-11-12
2.12.0	5 / 4	2024-02-28
2.11.0	5 / 4	2024-01-04
2.10.3	5 / 4	2023-11-15
2.10.2	5 / 4	2023-11-02
2.10.1	5 / 4	2023-10-24
2.10.0	5 / 4	2023-10-11
2.9.3	5 / 4	2023-06-25
2.9.2	5 / 4	2023-06-08
2.9.1	5 / 4	2023-05-27
2.9.0	5 / 4	2023-05-26
2.8.3	5 / 4	2023-01-18
2.8.2	5 / 4	2022-12-14
2.8.1	5 / 4	2022-12-08
2.8.0	5 / 4	2022-11-09
2.7.0	5 / 4	2022-08-03
2.6.2	5 / 4	2022-06-22
2.6.1	5 / 4	2022-06-17
2.6.0	5 / 5	2022-05-25
2.5.0	5 / 5	2022-04-21
2.4.1	5 / 5	2022-03-31
2.4.0	5 / 5	2022-03-22
2.3.2	5 / 5	2022-02-18
2.3.1	5 / 5	2022-02-10
2.3.0	5 / 5	2022-02-09
2.2.1	12 / 0	2022-01-17
2.2.0	12 / 0	2022-01-12
2.1.1	12 / 0	2022-01-06
2.1.0	12 / 0	2022-01-05
2.0.1	12 / 0	2021-11-08
2.0.0	12 / 0	2021-10-13
1.11.0	3 / 0	2018-12-18

v2.16.4

1 finding

LOW No provenance attestation provenance

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

v2.16.3

1 finding

LOW No provenance attestation provenance

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

v2.16.2

1 finding

LOW No provenance attestation provenance

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

v2.16.1

1 finding

LOW No provenance attestation provenance

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

v2.16.0

1 finding

LOW No provenance attestation provenance

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

v2.15.4

1 finding

LOW No provenance attestation provenance

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

v2.15.3

1 finding

LOW No provenance attestation provenance

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

v2.15.2

1 finding

LOW No provenance attestation provenance

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

v2.15.1

1 finding

LOW No provenance attestation provenance

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

v2.15.0

1 finding

LOW No provenance attestation provenance

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

v2.14.4

1 finding

LOW No provenance attestation provenance

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

v2.14.3

1 finding

LOW No provenance attestation provenance

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

v2.14.2

1 finding

LOW No provenance attestation provenance

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

v2.14.1

1 finding

LOW No provenance attestation provenance

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

v2.14.0

1 finding

LOW No provenance attestation provenance

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

v2.13.3

1 finding

LOW No provenance attestation provenance

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

v2.13.2

1 finding

LOW No provenance attestation provenance

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

v2.13.1

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.3

1 finding

LOW No provenance attestation provenance

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

v2.10.2

1 finding

LOW No provenance attestation provenance

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

v2.10.1

1 finding

LOW No provenance attestation provenance

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

v2.10.0

1 finding

LOW No provenance attestation provenance

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

v2.9.3

1 finding

LOW No provenance attestation provenance

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

v2.9.2

1 finding

LOW No provenance attestation provenance

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

v2.9.1

1 finding

LOW No provenance attestation provenance

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

v2.9.0

1 finding

LOW No provenance attestation provenance

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

v2.8.3

1 finding

LOW No provenance attestation provenance

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

v2.8.2

1 finding

LOW No provenance attestation provenance

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

v2.8.1

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@parcel/fs' is 1 edit(s) away from popular package 'qs'.

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.

v2.8.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@parcel/fs' is 1 edit(s) away from popular package 'qs'.

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.

v2.7.0

1 finding

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.

v2.6.2

1 finding

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.

v2.6.1

1 finding

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.

v2.6.0

1 finding

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.

v2.5.0

1 finding

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.

v2.4.1

1 finding

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.

v2.4.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@parcel/fs' is 1 edit(s) away from popular package 'qs'.

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.

v2.3.2

1 finding

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.

v2.3.1

1 finding

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.

v2.3.0

1 finding

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.

v2.2.1

1 finding

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.

v2.2.0

1 finding

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.

v2.1.1

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@parcel/fs' is 1 edit(s) away from popular package 'qs'.

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.

v2.1.0

1 finding

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.

v2.0.1

1 finding

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.

v2.0.0

1 finding

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.

v1.11.0

1 finding

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.