@kopexa/theme
The default theme for Kopexa 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Theme package; deps used in config/plugin files, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:flat | AI (phantom-deps): Used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:color | AI (phantom-deps): Used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:color2k | AI (phantom-deps): Used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tw-animate-css | AI (phantom-deps): CSS utility; used in config/styles, not directly imported. | ai | |
| phantom-deps | phantom-dep:@kopexa/shared-utils | AI (phantom-deps): Same org scope; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-node-range | AI (phantom-deps): Used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-drag-handle | AI (phantom-deps): Used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-drag-handle-react | AI (phantom-deps): Used in config files; stable false positive for this package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 17.32.4 | 12 / 4 | |
| 17.32.3 | 12 / 4 | |
| 17.32.2 | 12 / 4 | |
| 17.32.1 | 12 / 4 | |
| 17.31.3 | 12 / 4 | |
| 17.31.2 | 12 / 4 | |
| 17.31.1 | 12 / 4 | |
| 17.31.0 | 12 / 4 | |
| 17.30.0 | 12 / 4 | |
| 17.29.1 | 12 / 4 | |
| 17.29.0 | 12 / 4 | |
| 17.28.0 | 12 / 4 | |
| 17.27.3 | 12 / 4 | |
| 17.27.2 | 12 / 4 | |
| 17.27.1 | 12 / 4 | |
| 17.27.0 | 12 / 4 | |
| 17.26.10 | 12 / 4 | |
| 17.26.9 | 12 / 4 | |
| 17.26.8 | 12 / 4 | |
| 17.17.2 | 12 / 4 | |
| 17.17.1 | 12 / 4 | |
| 17.17.0 | 12 / 4 | |
| 17.16.0 | 12 / 4 | |
| 17.15.0 | 12 / 4 | |
| 17.14.0 | 12 / 4 | |
| 17.13.1 | 12 / 4 | |
| 17.13.0 | 12 / 4 | |
| 17.12.0 | 12 / 4 | |
| 17.11.4 | 12 / 4 | |
| 17.11.3 | 12 / 4 | |
| 17.11.2 | 12 / 4 | |
| 17.11.1 | 12 / 4 | |
| 17.11.0 | 12 / 4 | |
| 17.10.0 | 12 / 4 | |
| 17.9.0 | 11 / 4 | |
| 17.8.2 | 11 / 4 | |
| 17.8.1 | 11 / 4 | |
| 17.8.0 | 11 / 4 | |
| 17.7.0 | 11 / 4 | |
| 17.6.0 | 11 / 4 | |
| 17.5.0 | 11 / 4 | |
| 17.4.2 | 11 / 4 | |
| 17.4.1 | 11 / 4 | |
| 17.4.0 | 11 / 4 | |
| 17.3.0 | 11 / 4 | |
| 17.2.0 | 11 / 4 | |
| 17.1.2 | 11 / 4 | |
| 17.0.2 | 10 / 4 | |
| 17.0.1 | 10 / 4 | |
| 17.0.0 | 10 / 4 | |
| 16.0.0 | 10 / 4 |
v17.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.