@react-native-windows/find-repo-root
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft org account; addition consistent with internal CI/CD pipeline changes for this established package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 155 versions and is part of the Microsoft react-native-windows monorepo; version gaps reflect release cadence, not account takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo utility package from Microsoft; missing description is a known pattern for such packages and not a malware indicator. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is a declared runtime dependency in package.json; phantom-dep flag likely reflects indirect/config usage rather than a real issue for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package; lack of Sigstore provenance is common and not a risk signal given the publisher's track record. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.83.0 | 3 / 10 | |
| 0.82.0 | 3 / 10 | |
| 0.81.1 | 2 / 10 | |
| 0.81.0 | 2 / 10 | |
| 0.80.1 | 2 / 10 | |
| 0.80.0 | 2 / 10 | |
| 0.79.1 | 2 / 10 | |
| 0.79.0 | 2 / 10 | |
| 0.78.1 | 2 / 10 |
v0.83.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.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.80.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.79.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.79.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.78.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.