@ornikar/repo-config-react-legacy-css
🔧⚛️ react repo config legacy css
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is org-affiliated with clean track record; repo URL consistent with known ornikar monorepo. | ai | |
| phantom-deps | phantom-dep:typed-css-modules | AI (phantom-deps): Config-only reference; expected pattern for a repo-config package that wires up tools without directly importing them. | ai | |
| phantom-deps | phantom-dep:@ornikar/typed-css-modules-loader | AI (phantom-deps): Same-org loader declared as dep for downstream consumers; not directly imported by design. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 15.1.0 | 3 / 0 | |
| 15.0.5 | 3 / 0 | |
| 15.0.2 | 3 / 0 | |
| 15.0.1 | 3 / 0 | |
| 15.0.0 | 3 / 0 |
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.