@ornikar/repo-config
🔧 repo 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:prettier-plugin-properties | AI (dependencies): Pinned at 0.3.0, used as a prettier plugin config; stable pattern for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived ornikar org package with consistent history; publisher has prior approvals in same org scope. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves @commitlint/cli's own bin path; not arbitrary module loading. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@ornikar/commitlint-config | AI (phantom-deps): Config-only dep consumed by commitlint tooling, not directly imported in JS. Same org scope. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-properties | AI (phantom-deps): Prettier plugin referenced in config files, not imported directly. Expected pattern for prettier plugins. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 15.3.1 | 7 / 0 | |
| 15.3.0 | 7 / 0 | |
| 15.2.1 | 7 / 0 | |
| 15.2.0 | 7 / 0 | |
| 15.1.1 | 7 / 0 | |
| 15.1.0 | 7 / 0 | |
| 15.0.0 | 7 / 0 |
v15.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.