@htmlbricks/hb-area-code
Frameless code area (no Bulma `box`): copy + optional success tag floated top-right over the `<pre><code>` snippet; `:host` and root wrapper have no margin or padding. Copy dispatches `clipboardCopyText` with `{ text }`. Theme follows `bulma-wc-host-theme
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): Reflect.get usage is from Svelte's compiled IIFE bundle, not intentional obfuscation; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped web-component package with self-contained IIFE; no repo/keywords/deps is consistent with this package family. | ai |
Versions (showing 43 of 243)
| Version | Deps | Published |
|---|---|---|
| 0.60.46 | 0 / 0 | |
| 0.60.45 | 0 / 0 | |
| 0.60.44 | 0 / 0 | |
| 0.60.43 | 0 / 0 | |
| 0.60.41 | 0 / 0 | |
| 0.60.40 | 0 / 0 | |
| 0.60.39 | 0 / 0 | |
| 0.60.37 | 0 / 0 | |
| 0.60.36 | 0 / 0 | |
| 0.60.35 | 0 / 0 | |
| 0.60.33 | 0 / 0 | |
| 0.60.32 | 0 / 0 | |
| 0.60.31 | 0 / 0 | |
| 0.60.29 | 0 / 0 | |
| 0.60.28 | 0 / 0 | |
| 0.60.27 | 0 / 0 | |
| 0.60.26 | 0 / 0 | |
| 0.60.25 | 0 / 0 | |
| 0.60.24 | 0 / 0 | |
| 0.60.23 | 0 / 0 | |
| 0.60.22 | 0 / 0 | |
| 0.60.21 | 0 / 0 | |
| 0.60.20 | 0 / 0 | |
| 0.60.19 | 0 / 0 | |
| 0.60.18 | 0 / 0 | |
| 0.60.17 | 0 / 0 | |
| 0.60.16 | 0 / 0 | |
| 0.60.15 | 0 / 0 | |
| 0.60.14 | 0 / 0 | |
| 0.60.13 | 0 / 0 | |
| 0.60.12 | 0 / 0 | |
| 0.60.11 | 0 / 0 | |
| 0.60.10 | 0 / 0 | |
| 0.60.9 | 0 / 0 | |
| 0.60.8 | 0 / 0 | |
| 0.60.7 | 0 / 0 | |
| 0.60.6 | 0 / 0 | |
| 0.60.5 | 0 / 0 | |
| 0.60.4 | 0 / 0 | |
| 0.60.3 | 0 / 0 | |
| 0.60.2 | 0 / 0 | |
| 0.60.1 | 0 / 0 | |
| 0.60.0 | 0 / 0 |
v0.60.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.