@citygross/components
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long history; provenance absence is common and not a disqualifier here. | ai | |
| dependencies | unvetted-dep:@citygross/typography | AI (dependencies): Same-org scoped dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@citygross/utils | AI (dependencies): Same-org scoped dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@citygross/design-tokens | AI (dependencies): Same-org scoped dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@citygross/react-use-bg-wizard | AI (dependencies): Same-org scoped dep; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): moment is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org component library; missing metadata is expected for private/scoped packages, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:slick-carousel | AI (phantom-deps): slick-carousel is a CSS/asset dependency of react-slick; imported via config/styles, not JS imports. | ai | |
| phantom-deps | phantom-dep:@citygross/react-use-bg-wizard | AI (phantom-deps): Same-org dep; may be used indirectly or re-exported; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is consistent across all @citygross/* packages. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 0.18.4 | 8 / 30 | |
| 0.18.3 | 8 / 30 | |
| 0.18.2 | 8 / 30 | |
| 0.18.0 | 8 / 30 | |
| 0.17.13 | 8 / 30 | |
| 0.17.12 | 8 / 30 | |
| 0.17.10 | 8 / 30 | |
| 0.17.8 | 8 / 30 | |
| 0.17.5 | 8 / 30 | |
| 0.17.3 | 8 / 30 | |
| 0.17.2 | 8 / 29 | |
| 0.16.27 | 9 / 29 | |
| 0.16.26 | 9 / 29 | |
| 0.16.25 | 9 / 29 | |
| 0.16.24 | 9 / 29 | |
| 0.16.23 | 9 / 29 | |
| 0.16.22 | 9 / 29 | |
| 0.16.21 | 9 / 29 | |
| 0.16.20 | 9 / 29 | |
| 0.16.17 | 9 / 29 | |
| 0.16.13 | 9 / 29 | |
| 0.16.10 | 10 / 29 | |
| 0.16.9 | 10 / 29 | |
| 0.16.7 | 10 / 29 | |
| 0.16.6 | 10 / 29 | |
| 0.16.5 | 10 / 29 | |
| 0.16.4 | 10 / 29 | |
| 0.16.1 | 10 / 29 | |
| 0.16.0 | 10 / 29 | |
| 0.15.4 | 10 / 29 | |
| 0.15.2 | 10 / 29 | |
| 0.15.1 | 10 / 29 | |
| 0.15.0 | 10 / 29 | |
| 0.14.13 | 10 / 29 | |
| 0.14.12 | 10 / 29 | |
| 0.14.7 | 10 / 29 | |
| 0.14.5 | 10 / 29 | |
| 0.14.2 | 10 / 29 | |
| 0.14.0 | 10 / 29 | |
| 0.13.19 | 10 / 29 | |
| 0.13.17 | 10 / 29 | |
| 0.13.16 | 10 / 29 | |
| 0.13.15 | 10 / 29 | |
| 0.13.12 | 10 / 29 | |
| 0.13.10 | 10 / 29 | |
| 0.13.8 | 10 / 29 | |
| 0.13.1 | 10 / 29 | |
| 0.12.9 | 10 / 29 | |
| 0.12.8 | 10 / 29 | |
| 0.12.5 | 10 / 29 | |
| 0.12.3 | 10 / 29 |
v0.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.