@microsoft/node-core-library
(Please use "@rushstack/node-core-library" instead.)
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): node-core-library's Executable.js legitimately wraps child_process for toolchain process execution utilities; this is documented, expected behavior for this package. | ai | |
| phantom-deps | phantom-dep:@types/jju | AI (phantom-deps): @types/* packages are TypeScript type definitions declared as deps by convention in older TS projects; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a TypeScript type definition package; phantom-dep firing on it is a stable false positive for any TypeScript package. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): @types/fs-extra is a TypeScript type definition package; phantom-dep firing on it is a stable false positive for any TypeScript package. | ai | |
| phantom-deps | phantom-dep:@types/z-schema | AI (phantom-deps): @types/z-schema is a TypeScript type definition package; phantom-dep firing on it is a stable false positive for any TypeScript package. | ai |
Versions (showing 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 6 / 6 | |
| 0.2.11 | 6 / 6 | |
| 0.2.10 | 6 / 6 | |
| 0.2.9 | 6 / 6 | |
| 0.2.8 | 6 / 6 | |
| 0.2.7 | 7 / 6 | |
| 0.2.6 | 7 / 6 | |
| 0.2.5 | 7 / 6 | |
| 0.2.4 | 7 / 6 | |
| 0.2.3 | 7 / 6 | |
| 0.2.2 | 7 / 6 | |
| 0.2.1 | 7 / 6 | |
| 0.2.0 | 7 / 6 |
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.