@kopexa/tooltip
Floating element that provides a control with contextual information via pointer or focus.
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:@base-ui-components/react | AI (phantom-deps): Declared as a runtime dep; phantom-dep heuristic fires because it's not directly imported in analyzed sources, but it's a legitimate dependency. | ai | |
| phantom-deps | phantom-dep:@kopexa/react-utils | AI (phantom-deps): Same-org monorepo dep; phantom detection likely a false positive from build bundling. | ai | |
| phantom-deps | phantom-dep:@kopexa/shared-utils | AI (phantom-deps): Same-org monorepo dep; phantom detection likely a false positive from build bundling. | ai | |
| phantom-deps | phantom-dep:@kopexa/use-controllable-state | AI (phantom-deps): Same-org monorepo dep; phantom detection likely a false positive from build bundling. | ai | |
| phantom-deps | phantom-dep:@base-ui/react | AI (phantom-deps): Referenced in config/type files; common pattern for UI component packages. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 17.2.55 | 5 / 0 | |
| 17.2.54 | 5 / 0 | |
| 17.2.53 | 5 / 0 | |
| 17.2.52 | 5 / 0 | |
| 17.2.50 | 5 / 0 | |
| 17.2.49 | 5 / 0 | |
| 17.2.48 | 5 / 0 | |
| 17.2.47 | 5 / 0 | |
| 17.2.46 | 5 / 0 | |
| 17.2.45 | 5 / 0 | |
| 17.2.44 | 5 / 0 | |
| 17.2.43 | 5 / 0 | |
| 17.2.42 | 5 / 0 | |
| 17.2.41 | 5 / 0 | |
| 17.2.40 | 5 / 0 | |
| 17.2.39 | 5 / 0 | |
| 17.2.38 | 5 / 0 | |
| 17.2.37 | 5 / 0 | |
| 17.2.36 | 5 / 0 | |
| 17.1.4 | 5 / 0 | |
| 17.1.3 | 5 / 0 | |
| 17.1.2 | 5 / 0 | |
| 17.1.1 | 5 / 0 | |
| 17.1.0 | 5 / 0 | |
| 17.0.1 | 5 / 0 | |
| 14.0.4 | 5 / 0 |
v17.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.3
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.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.