@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, 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 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 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.84.0 | 3 / 10 | |
| 0.83.1 | 3 / 10 | |
| 0.83.0 | 3 / 10 | |
| 0.82.1 | 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 | |
| 0.78.0 | 2 / 10 | |
| 0.77.1 | 2 / 10 | |
| 0.77.0 | 2 / 10 | |
| 0.76.1 | 2 / 10 | |
| 0.76.0 | 2 / 10 | |
| 0.75.2 | 2 / 10 | |
| 0.75.1 | 2 / 10 | |
| 0.75.0 | 2 / 10 | |
| 0.74.1 | 2 / 10 | |
| 0.74.0 | 2 / 10 | |
| 0.73.1 | 2 / 10 | |
| 0.73.0 | 2 / 10 | |
| 0.72.1 | 2 / 10 | |
| 0.72.0 | 2 / 10 | |
| 0.71.3 | 2 / 10 | |
| 0.71.2 | 2 / 10 | |
| 0.71.1 | 4 / 8 | |
| 0.71.0 | 4 / 8 | |
| 0.70.2 | 2 / 10 | |
| 0.70.1 | 4 / 8 | |
| 0.70.0 | 4 / 8 | |
| 0.69.2 | 2 / 11 | |
| 0.69.1 | 4 / 9 | |
| 0.69.0 | 4 / 9 | |
| 0.68.1 | 1 / 9 | |
| 0.68.0 | 1 / 9 | |
| 0.67.0 | 1 / 9 | |
| 0.66.1 | 1 / 9 | |
| 0.66.0 | 1 / 9 | |
| 0.65.1 | 1 / 9 | |
| 0.65.0 | 1 / 9 | |
| 0.64.1 | 1 / 8 | |
| 0.64.0 | 1 / 8 |
v0.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.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.73.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.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.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.