@ornikar/monorepo-config
📚 monorepo config
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lerna-lite/cli | AI (dependencies): Legitimate replacement for deprecated @lerna/cli; expected for a monorepo config package. | ai | |
| dependencies | unvetted-dep:@lerna-lite/version | AI (dependencies): Legitimate replacement for deprecated @lerna/version; expected for a monorepo config package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-specified prettier config by path in a CLI tool; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:conventional-changelog-conventionalcommits | AI (phantom-deps): Listed as a direct dependency and used via config reference; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 14.3.0 | 4 / 0 | |
| 14.2.1 | 4 / 0 | |
| 14.2.0 | 4 / 0 | |
| 14.1.0 | 4 / 0 | |
| 14.0.0 | 4 / 0 |
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.