@rnx-kit/console
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
jasonvmorseacoatesrnbottido64rnsdkbothansenyymicrosoft-oss-releasesmicrosoft1es
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 org-level maintainers added as part of rnx-kit publishing consolidation; stable pattern for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Individual maintainer removed in favor of org bot accounts; consistent with Microsoft OSS publishing practices. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects org publishing consolidation, not account takeover; no code changes and publisher has clean track record. | ai |
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.