@c-rex/utils
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo internal utility; no description/repo/keywords is normal for scoped packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped internal utility; description omission is benign in monorepo context. | ai | |
| phantom-deps | phantom-dep:nuqs | AI (phantom-deps): nuqs is a declared runtime dep used via re-exports or config; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@c-rex/constants | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic commonly misfires on intra-monorepo deps. | ai | |
| phantom-deps | phantom-dep:country-flag-icons | AI (phantom-deps): Declared runtime dep referenced in config files; stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.1.21 | 8 / 10 | |
| 0.1.20 | 8 / 10 | |
| 0.1.19 | 8 / 10 | |
| 0.1.18 | 8 / 10 | |
| 0.1.17 | 8 / 10 | |
| 0.1.16 | 8 / 10 | |
| 0.1.15 | 8 / 10 | |
| 0.1.14 | 8 / 10 | |
| 0.1.13 | 8 / 10 | |
| 0.1.12 | 8 / 10 | |
| 0.1.11 | 8 / 10 | |
| 0.1.10 | 8 / 10 | |
| 0.1.9 | 8 / 10 | |
| 0.1.8 | 8 / 10 | |
| 0.1.7 | 8 / 10 | |
| 0.1.6 | 8 / 10 | |
| 0.1.5 | 8 / 10 | |
| 0.1.4 | 8 / 10 | |
| 0.1.3 | 8 / 10 | |
| 0.1.2 | 8 / 10 | |
| 0.1.1 | 8 / 10 | |
| 0.1.0 | 8 / 10 | |
| 0.0.8 | 3 / 10 | |
| 0.0.7 | 3 / 10 |
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.