@react-native-windows/automation-commands
Allows controlling your react-native-windows application
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config reference only, not a runtime import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint config reference only, not a runtime import; stable false positive for this package. | ai |
Versions (showing 100 of 641)
| Version | Deps | Published |
|---|---|---|
| 0.84.0 | 3 / 9 | |
| 0.83.2 | 3 / 9 | |
| 0.83.0 | 3 / 9 | |
| 0.82.8 | 3 / 9 | |
| 0.82.5 | 3 / 9 | |
| 0.81.32 | 3 / 9 | |
| 0.81.31 | 3 / 9 | |
| 0.81.30 | 3 / 9 | |
| 0.81.29 | 3 / 9 | |
| 0.81.28 | 3 / 9 | |
| 0.81.27 | 3 / 9 | |
| 0.81.26 | 3 / 9 | |
| 0.81.25 | 3 / 9 | |
| 0.81.24 | 3 / 9 | |
| 0.81.22 | 3 / 9 | |
| 0.81.21 | 3 / 9 | |
| 0.81.20 | 3 / 9 | |
| 0.81.19 | 3 / 9 | |
| 0.81.18 | 3 / 9 | |
| 0.81.15 | 3 / 9 | |
| 0.81.13 | 3 / 9 | |
| 0.81.12 | 3 / 9 | |
| 0.81.11 | 3 / 9 | |
| 0.81.10 | 3 / 9 | |
| 0.1.446 | 3 / 9 | |
| 0.1.445 | 3 / 9 | |
| 0.1.444 | 3 / 9 | |
| 0.1.443 | 3 / 9 | |
| 0.1.442 | 3 / 9 | |
| 0.1.441 | 3 / 9 | |
| 0.1.440 | 3 / 9 | |
| 0.1.439 | 3 / 9 | |
| 0.1.438 | 3 / 9 | |
| 0.1.437 | 3 / 9 | |
| 0.1.436 | 3 / 9 | |
| 0.1.435 | 3 / 9 | |
| 0.1.434 | 3 / 9 | |
| 0.1.433 | 3 / 9 | |
| 0.1.432 | 3 / 9 | |
| 0.1.431 | 3 / 9 | |
| 0.1.430 | 3 / 9 | |
| 0.1.429 | 3 / 9 | |
| 0.1.428 | 3 / 9 | |
| 0.1.427 | 3 / 9 | |
| 0.1.426 | 3 / 9 | |
| 0.1.425 | 3 / 9 | |
| 0.1.424 | 3 / 9 | |
| 0.1.423 | 3 / 9 | |
| 0.1.422 | 3 / 9 | |
| 0.1.421 | 3 / 9 | |
| 0.1.420 | 3 / 9 | |
| 0.1.419 | 3 / 9 | |
| 0.1.418 | 3 / 9 | |
| 0.1.417 | 3 / 9 | |
| 0.1.416 | 3 / 9 | |
| 0.1.415 | 3 / 9 | |
| 0.1.414 | 3 / 9 | |
| 0.1.413 | 3 / 9 | |
| 0.1.412 | 3 / 9 | |
| 0.1.411 | 3 / 9 | |
| 0.1.410 | 3 / 9 | |
| 0.1.409 | 3 / 9 | |
| 0.1.408 | 3 / 9 | |
| 0.1.407 | 3 / 9 | |
| 0.1.406 | 3 / 9 | |
| 0.1.405 | 3 / 9 | |
| 0.1.404 | 3 / 9 | |
| 0.1.403 | 3 / 9 | |
| 0.1.402 | 3 / 9 | |
| 0.1.401 | 3 / 9 | |
| 0.1.400 | 3 / 9 | |
| 0.1.399 | 3 / 9 | |
| 0.1.398 | 3 / 9 | |
| 0.1.397 | 3 / 9 | |
| 0.1.396 | 3 / 9 | |
| 0.1.395 | 3 / 9 | |
| 0.1.394 | 3 / 9 | |
| 0.1.393 | 3 / 9 | |
| 0.1.392 | 3 / 9 | |
| 0.1.391 | 3 / 9 | |
| 0.1.390 | 3 / 9 | |
| 0.1.389 | 3 / 9 | |
| 0.1.388 | 3 / 9 | |
| 0.1.387 | 3 / 9 | |
| 0.1.386 | 3 / 9 | |
| 0.1.385 | 3 / 9 | |
| 0.1.384 | 3 / 9 | |
| 0.1.383 | 3 / 9 | |
| 0.1.382 | 3 / 9 | |
| 0.1.381 | 3 / 9 | |
| 0.1.380 | 3 / 9 | |
| 0.1.379 | 3 / 9 | |
| 0.1.378 | 3 / 9 | |
| 0.1.377 | 3 / 9 | |
| 0.1.376 | 3 / 9 | |
| 0.1.375 | 3 / 9 | |
| 0.1.374 | 3 / 9 | |
| 0.1.373 | 3 / 9 | |
| 0.1.372 | 3 / 9 | |
| 0.1.371 | 3 / 9 |
v0.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.390
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.389
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.388
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.386
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.385
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.384
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.383
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.382
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.381
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.380
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.379
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.378
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.376
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.375
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.374
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.373
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.