@yarn-tool/ncu
A wrapper tool for npm-check-updates that checks and updates package dependencies with semver support, version caching, and yarn.lock resolutions integration. Provides CLI options, table output, and efficient batch processing for monorepo workflows. 封裝 np
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@yarn-tool/semver-diff | AI (phantom-deps): Same-org sibling dep; declared in package.json, likely used transitively or conditionally within the monorepo. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.0.9 | 14 / 0 | |
| 3.0.8 | 14 / 0 | |
| 3.0.7 | 14 / 0 | |
| 3.0.5 | 14 / 0 | |
| 3.0.4 | 14 / 0 | |
| 3.0.3 | 14 / 0 |
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.