@thi.ng/rdom
Lightweight, reactive, VDOM-less UI/DOM components with async lifecycle and @thi.ng/hiccup compatible
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/rdom is a legitimate scoped package in the thi.ng/umbrella monorepo, not a typosquat of jsdom. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/paths | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/hiccup | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/rstream | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@thi.ng/strings | AI (dependencies): Sibling package in the thi.ng/umbrella monorepo; stable dependency. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 2.0.6 | 8 / 3 | |
| 2.0.5 | 8 / 3 | |
| 2.0.4 | 8 / 3 | |
| 2.0.2 | 8 / 3 | |
| 2.0.1 | 8 / 3 | |
| 1.7.89 | 8 / 3 | |
| 1.7.88 | 8 / 3 | |
| 1.7.87 | 8 / 3 | |
| 1.7.86 | 8 / 3 | |
| 1.7.85 | 8 / 3 | |
| 1.7.84 | 8 / 3 | |
| 1.7.83 | 8 / 3 | |
| 1.7.82 | 8 / 3 | |
| 1.7.81 | 8 / 3 | |
| 1.7.80 | 8 / 3 | |
| 1.7.79 | 8 / 3 | |
| 1.7.78 | 8 / 3 | |
| 1.7.77 | 8 / 3 | |
| 1.7.76 | 8 / 3 | |
| 1.7.74 | 8 / 3 | |
| 1.7.73 | 8 / 3 | |
| 1.7.72 | 8 / 3 | |
| 1.7.71 | 8 / 3 | |
| 1.7.70 | 8 / 3 | |
| 1.7.69 | 8 / 3 | |
| 1.7.68 | 8 / 3 | |
| 1.7.67 | 8 / 3 | |
| 1.7.66 | 8 / 3 | |
| 1.7.65 | 8 / 3 | |
| 1.7.64 | 8 / 3 | |
| 1.7.60 | 8 / 3 | |
| 1.7.59 | 8 / 3 | |
| 1.7.58 | 8 / 3 | |
| 1.7.57 | 8 / 3 | |
| 1.7.56 | 8 / 3 | |
| 1.7.55 | 8 / 3 | |
| 1.7.54 | 8 / 3 | |
| 1.7.53 | 8 / 3 | |
| 1.7.52 | 8 / 3 | |
| 1.7.51 | 8 / 3 | |
| 1.7.50 | 8 / 3 | |
| 1.7.49 | 8 / 3 | |
| 1.7.48 | 8 / 3 | |
| 1.7.47 | 8 / 3 | |
| 1.7.46 | 8 / 3 | |
| 1.7.45 | 8 / 3 | |
| 1.7.44 | 8 / 3 | |
| 1.7.43 | 8 / 3 | |
| 1.7.42 | 8 / 3 | |
| 1.7.41 | 8 / 3 | |
| 1.7.40 | 8 / 3 |
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.