@thi.ng/hdom
Lightweight vanilla ES6 UI component trees with customizable branch-local behaviors
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jsdom | AI (typosquat): @thi.ng/hdom is a legitimate scoped package in the thi.ng/umbrella monorepo, not a typosquat of jsdom. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 9.4.116 | 8 / 4 | |
| 9.4.115 | 8 / 4 | |
| 9.4.114 | 8 / 4 | |
| 9.4.112 | 8 / 4 | |
| 9.4.111 | 8 / 4 | |
| 9.4.110 | 8 / 4 | |
| 9.4.109 | 8 / 4 | |
| 9.4.108 | 8 / 4 | |
| 9.4.107 | 8 / 4 | |
| 9.4.106 | 8 / 4 | |
| 9.4.105 | 8 / 4 | |
| 9.4.104 | 8 / 4 | |
| 9.4.103 | 8 / 4 | |
| 9.4.102 | 8 / 4 | |
| 9.4.101 | 8 / 4 | |
| 9.4.100 | 8 / 4 | |
| 9.4.99 | 8 / 4 | |
| 9.4.98 | 8 / 4 | |
| 9.4.97 | 8 / 4 | |
| 9.4.96 | 8 / 4 | |
| 9.4.95 | 8 / 4 | |
| 9.4.94 | 8 / 4 | |
| 9.4.93 | 8 / 4 | |
| 9.4.92 | 8 / 4 | |
| 9.4.91 | 8 / 4 | |
| 9.4.87 | 8 / 4 | |
| 9.4.86 | 8 / 4 | |
| 9.4.85 | 8 / 4 | |
| 9.4.84 | 8 / 4 | |
| 9.4.83 | 8 / 4 | |
| 9.4.82 | 8 / 4 | |
| 9.4.81 | 8 / 4 | |
| 9.4.80 | 8 / 4 | |
| 9.4.79 | 8 / 4 | |
| 9.4.78 | 8 / 4 | |
| 9.4.77 | 8 / 4 | |
| 9.4.76 | 8 / 4 | |
| 9.4.75 | 8 / 4 | |
| 9.4.74 | 8 / 4 | |
| 9.4.73 | 8 / 4 | |
| 9.4.72 | 8 / 4 |
v9.4.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.