@kopexa/tiptap
our tiptap 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@kopexa/dialog | AI (dependencies): Same org scope (@kopexa); consistent with the rest of the dependency set. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used library; its use in a tiptap editor component is expected and benign. | ai | |
| phantom-deps | phantom-dep:@kopexa/callout | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@kopexa/use-composed-ref | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:jsx-dom-cjs | AI (phantom-deps): Referenced in config files only; stable false positive for this build setup. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-task-item | AI (phantom-deps): Config-file reference; stable false positive for this tiptap extension bundle. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-task-list | AI (phantom-deps): Config-file reference; stable false positive for this tiptap extension bundle. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-mathematics | AI (phantom-deps): Config-file reference; stable false positive for this tiptap extension bundle. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Referenced in config files; transitive/indirect usage pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@kopexa/tabs | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on bundled/re-exported packages. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package; provenance absence is common and not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 17.12.22 | 57 / 0 | |
| 17.12.21 | 57 / 0 | |
| 17.12.20 | 57 / 0 | |
| 17.12.15 | 57 / 0 | |
| 17.12.14 | 57 / 0 | |
| 17.12.13 | 57 / 0 | |
| 17.12.7 | 57 / 0 | |
| 17.12.5 | 57 / 0 | |
| 17.12.3 | 57 / 0 | |
| 17.8.1 | 58 / 0 | |
| 17.1.0 | 51 / 0 | |
| 14.0.4 | 43 / 0 |
v17.12.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.12.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.12.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.12.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.