@react-native-windows/fs
A minimal-dependency drop-in replacement to `fs` with changes for resiliency, promises, and convenience.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft org automation account; addition is consistent with internal CI pipeline changes. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @react-native-windows/fs is a legitimate Microsoft package; Levenshtein comparison to 'qs' is a false positive due to short target name. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @react-native-windows/fs is a legitimate Microsoft package; Levenshtein comparison to 'pg' is a false positive due to short target name. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is a declared runtime dependency in package.json; phantom-dep finding reflects indirect/config usage, not a security concern. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.84.0 | 2 / 10 | |
| 0.83.1 | 2 / 10 | |
| 0.83.0 | 2 / 10 | |
| 0.82.1 | 2 / 10 | |
| 0.82.0 | 2 / 10 | |
| 0.81.1 | 1 / 10 | |
| 0.81.0 | 1 / 10 | |
| 0.80.1 | 1 / 10 | |
| 0.80.0 | 1 / 10 | |
| 0.79.1 | 1 / 10 | |
| 0.79.0 | 1 / 10 | |
| 0.78.1 | 1 / 10 | |
| 0.78.0 | 1 / 10 | |
| 0.77.1 | 1 / 10 | |
| 0.77.0 | 1 / 10 | |
| 0.76.1 | 1 / 10 | |
| 0.76.0 | 1 / 10 | |
| 0.75.2 | 1 / 10 | |
| 0.75.1 | 1 / 10 | |
| 0.75.0 | 1 / 10 | |
| 0.74.1 | 1 / 10 | |
| 0.74.0 | 1 / 10 | |
| 0.73.1 | 1 / 10 | |
| 0.73.0 | 1 / 10 | |
| 0.72.1 | 1 / 10 | |
| 0.72.0 | 1 / 10 | |
| 0.71.3 | 1 / 10 | |
| 0.71.2 | 1 / 10 | |
| 0.71.1 | 3 / 8 | |
| 0.71.0 | 3 / 8 | |
| 0.70.2 | 1 / 10 | |
| 0.70.1 | 3 / 8 | |
| 0.70.0 | 3 / 8 | |
| 0.69.2 | 1 / 11 | |
| 0.69.1 | 3 / 9 | |
| 0.69.0 | 3 / 9 | |
| 0.68.1 | 1 / 9 | |
| 0.68.0 | 1 / 9 |
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.