@thi.ng/rdom-components
Collection of unstyled, customizable components for @thi.ng/rdom
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/rdom | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/rstream | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/strings | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/hiccup-html | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/object-utils | AI (dependencies): Sibling thi.ng/umbrella package from same trusted publisher. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.0.80 | 7 / 3 | |
| 1.0.79 | 7 / 3 | |
| 1.0.78 | 7 / 3 | |
| 1.0.76 | 7 / 3 | |
| 1.0.75 | 7 / 3 | |
| 1.0.73 | 7 / 3 | |
| 1.0.72 | 7 / 3 | |
| 1.0.71 | 7 / 3 | |
| 1.0.70 | 7 / 3 | |
| 1.0.69 | 7 / 3 | |
| 1.0.68 | 7 / 3 | |
| 1.0.67 | 7 / 3 | |
| 1.0.66 | 7 / 3 | |
| 1.0.65 | 7 / 3 | |
| 1.0.64 | 7 / 3 | |
| 1.0.63 | 7 / 3 | |
| 1.0.62 | 7 / 3 | |
| 1.0.61 | 7 / 3 | |
| 1.0.60 | 7 / 3 | |
| 1.0.58 | 7 / 3 | |
| 1.0.57 | 7 / 3 | |
| 1.0.56 | 7 / 3 | |
| 1.0.55 | 7 / 3 | |
| 1.0.54 | 7 / 3 | |
| 1.0.53 | 7 / 3 | |
| 1.0.52 | 7 / 3 | |
| 1.0.51 | 7 / 3 | |
| 1.0.50 | 7 / 3 | |
| 1.0.49 | 7 / 3 | |
| 1.0.48 | 7 / 3 | |
| 1.0.44 | 7 / 3 | |
| 1.0.43 | 7 / 3 | |
| 1.0.42 | 7 / 3 | |
| 1.0.41 | 7 / 3 | |
| 1.0.40 | 7 / 3 | |
| 1.0.39 | 7 / 3 | |
| 1.0.38 | 7 / 3 | |
| 1.0.36 | 7 / 3 | |
| 1.0.35 | 7 / 3 | |
| 1.0.34 | 7 / 3 | |
| 1.0.33 | 7 / 3 | |
| 1.0.32 | 7 / 3 | |
| 1.0.31 | 7 / 3 | |
| 1.0.30 | 7 / 3 | |
| 1.0.29 | 7 / 3 | |
| 1.0.28 | 7 / 3 | |
| 1.0.27 | 7 / 3 | |
| 1.0.26 | 7 / 3 | |
| 1.0.25 | 7 / 3 | |
| 1.0.24 | 7 / 3 | |
| 1.0.23 | 7 / 3 |
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.