@htmlbricks/hb-tooltip
Wraps slotted content with a Bootstrap-styled tooltip bubble driven by the `tooltip` JSON (title, placement, HTML mode, delays, etc.). Optional `show` can force visibility; emits `visualizationChange` when opened or closed.
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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Svelte IIFE compiler output routinely uses Reflect; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped component library in a monorepo; no repo/keywords/deps is consistent across all 134 versions. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 0.65.17 | 0 / 0 | |
| 0.65.16 | 0 / 0 | |
| 0.65.13 | 0 / 0 | |
| 0.65.11 | 0 / 0 | |
| 0.65.10 | 0 / 0 | |
| 0.65.8 | 0 / 0 | |
| 0.65.7 | 0 / 0 | |
| 0.65.6 | 0 / 0 | |
| 0.65.5 | 0 / 0 | |
| 0.65.4 | 0 / 0 | |
| 0.65.3 | 0 / 0 | |
| 0.65.2 | 0 / 0 | |
| 0.65.1 | 0 / 0 | |
| 0.65.0 | 0 / 0 | |
| 0.64.0 | 0 / 0 | |
| 0.62.33 | 0 / 0 | |
| 0.62.31 | 0 / 0 | |
| 0.62.30 | 0 / 0 | |
| 0.62.28 | 0 / 0 | |
| 0.62.26 | 0 / 0 | |
| 0.62.25 | 0 / 0 | |
| 0.62.14 | 0 / 0 | |
| 0.62.13 | 0 / 0 | |
| 0.62.11 | 0 / 0 | |
| 0.62.10 | 0 / 0 | |
| 0.62.9 | 0 / 0 | |
| 0.62.8 | 0 / 0 | |
| 0.62.7 | 0 / 0 | |
| 0.62.6 | 0 / 0 | |
| 0.62.5 | 0 / 0 | |
| 0.62.4 | 0 / 0 | |
| 0.62.3 | 0 / 0 | |
| 0.62.2 | 0 / 0 | |
| 0.62.1 | 0 / 0 |
v0.65.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.