q-fs
Q Promise wrappers for Node's file system.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is ~15 years old targeting node 0.2.0; 0.0.0 versioning was common in early Node.js era. Not a malicious indicator for this package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): q-fs is a legitimate Q Promise filesystem wrapper by Kris Kowal (author of the q library), not a typosquat of qs. The name match is purely coincidental. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is ~15 years old, predating modern README and keyword conventions. Sparse metadata is expected for packages of this era. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 0.1.36 | 3 / 1 | |
| 0.1.35 | 3 / 1 | |
| 0.1.34 | 3 / 1 | |
| 0.1.33 | 3 / 1 | |
| 0.1.32 | 3 / 1 | |
| 0.1.31 | 3 / 1 | |
| 0.1.30 | 3 / 1 | |
| 0.1.29 | 3 / 1 | |
| 0.1.28 | 3 / 1 | |
| 0.1.27 | 3 / 1 | |
| 0.1.26 | 3 / 1 | |
| 0.1.25 | 3 / 1 | |
| 0.1.24 | 4 / 1 | |
| 0.1.23 | 4 / 1 | |
| 0.1.22 | 4 / 1 | |
| 0.1.21 | 4 / 1 | |
| 0.1.19 | 4 / 1 | |
| 0.1.18 | 4 / 1 | |
| 0.1.17 | 4 / 1 | |
| 0.1.16 | 4 / 1 | |
| 0.1.15 | 4 / 1 | |
| 0.1.14 | 4 / 1 | |
| 0.1.13 | 4 / 1 | |
| 0.1.12 | 4 / 1 | |
| 0.1.11 | 4 / 1 | |
| 0.1.10 | 4 / 1 | |
| 0.1.9 | 4 / 1 | |
| 0.1.8 | 4 / 1 | |
| 0.1.7 | 4 / 1 | |
| 0.1.6 | 4 / 1 | |
| 0.1.5 | 4 / 1 | |
| 0.1.4 | 4 / 1 | |
| 0.1.3 | 4 / 1 | |
| 0.1.2 | 4 / 1 | |
| 0.1.1 | 4 / 1 | |
| 0.1.0 | 4 / 1 | |
| 0.0.16 | 4 / 0 | |
| 0.0.15 | 4 / 0 | |
| 0.0.14 | 4 / 0 | |
| 0.0.13 | 4 / 0 | |
| 0.0.12 | 4 / 0 | |
| 0.0.11 | 4 / 0 | |
| 0.0.10 | 4 / 0 | |
| 0.0.9 | 4 / 0 | |
| 0.0.7 | 4 / 0 | |
| 0.0.6 | 4 / 0 | |
| 0.0.5 | 4 / 0 | |
| 0.0.4 | 4 / 0 | |
| 0.0.3 | 4 / 0 | |
| 0.0.2 | 4 / 0 | |
| 0.0.1 | 4 / 0 |
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.