@react-native-windows/package-utils
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from rnbot to microsoft1es reflects a Microsoft-internal automation account transition; microsoft1es has a strong track record (3598 approved) and is a known Microsoft service account. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is consistent with this sub-package not requiring updates during the intervening period; the monorepo is actively maintained and the version aligns with the 0.80 release cycle. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is a side effect of the changed publish pipeline (new publisher account), not indicative of malicious activity for this well-established Microsoft package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo utility package from Microsoft; missing description is a cosmetic issue, not a security signal for this well-established publisher. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is a declared runtime dependency used in config/glob matching; phantom-dep flag is a packaging concern, not a security risk for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.83.0 | 5 / 10 | |
| 0.82.0 | 5 / 10 | |
| 0.81.1 | 4 / 10 | |
| 0.81.0 | 4 / 10 | |
| 0.80.1 | 4 / 10 | |
| 0.80.0 | 4 / 10 | |
| 0.79.1 | 4 / 10 | |
| 0.79.0 | 4 / 10 | |
| 0.78.1 | 4 / 10 |
v0.83.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
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
3 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.
This version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
3 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.
This version was published by a different npm account than previous versions on 2025-12-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
3 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.
This version was published by a different npm account than previous versions on 2025-12-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.