@itcase/ui-core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/runtime dep referenced in config; not directly imported in source is expected for a UI lib. | ai | |
| phantom-deps | phantom-dep:@emotion/is-prop-valid | AI (phantom-deps): Emotion utility referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@itcase/storybook-config | AI (phantom-deps): Same-org storybook config dep; used in build/config context, not directly imported in source. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.10.15 | 9 / 24 | |
| 1.10.14 | 9 / 24 | |
| 1.10.13 | 9 / 24 | |
| 1.10.12 | 9 / 24 | |
| 1.10.11 | 9 / 24 | |
| 1.10.10 | 9 / 24 | |
| 1.10.8 | 9 / 24 | |
| 1.10.7 | 9 / 24 | |
| 1.10.2 | 9 / 24 | |
| 1.10.1 | 9 / 24 | |
| 1.10.0 | 9 / 24 | |
| 1.9.108 | 9 / 24 | |
| 1.9.106 | 9 / 24 | |
| 1.9.105 | 9 / 24 | |
| 1.9.97 | 9 / 24 | |
| 1.9.96 | 9 / 24 | |
| 1.9.91 | 9 / 24 | |
| 1.9.90 | 9 / 25 | |
| 1.9.89 | 9 / 25 | |
| 1.9.88 | 9 / 25 | |
| 1.9.87 | 9 / 25 | |
| 1.9.86 | 9 / 25 | |
| 1.9.85 | 9 / 25 | |
| 1.9.84 | 9 / 25 | |
| 1.9.83 | 9 / 25 | |
| 1.9.82 | 9 / 25 | |
| 1.9.81 | 9 / 25 | |
| 1.9.77 | 10 / 25 |
v1.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.