@rnx-kit/tools-node
6
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
jasonvmorseacoatesrnbottido64rnsdkbothansenyymicrosoft-oss-releasesmicrosoft1es
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from rnsdkbot to GitHub Actions CI; both are Microsoft-controlled publishing identities. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature Microsoft package with SLSA provenance; dormancy reflects stable maintenance cadence. | ai | |
| dependencies | unvetted-dep:@rnx-kit/types-node | AI (dependencies): Sibling package in the same Microsoft rnx-kit monorepo; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.0.5 | 1 / 3 | |
| 3.0.4 | 1 / 4 | |
| 3.0.3 | 0 / 4 | |
| 3.0.2 | 0 / 7 | |
| 3.0.1 | 0 / 7 | |
| 3.0.0 | 0 / 7 |
v3.0.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.