@magic/fs
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @magic/fs is not a typosquat of unscoped 'qs'; stable FP for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @magic/fs is not a typosquat of unscoped 'pg'; stable FP for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.38 | 5 / 10 | |
| 0.0.37 | 5 / 10 | |
| 0.0.36 | 5 / 10 | |
| 0.0.35 | 5 / 10 | |
| 0.0.34 | 5 / 10 | |
| 0.0.33 | 5 / 10 | |
| 0.0.32 | 5 / 10 | |
| 0.0.31 | 5 / 8 |
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
2 findingsPackage name '@magic/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.