@thi.ng/hdiff
String diffing w/ hiccup output for further processing, e.g. with @thi.ng/hdom, @thi.ng/hiccup. Includes CLI util to generate HTML, with theme support and code folding
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 package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/diff | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/hiccup | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/strings | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/hiccup-css | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; same trusted publisher. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.2.51 | 5 / 4 | |
| 1.2.50 | 5 / 4 | |
| 1.2.49 | 5 / 4 | |
| 1.2.47 | 5 / 4 | |
| 1.2.46 | 5 / 4 | |
| 1.2.44 | 5 / 4 | |
| 1.2.43 | 5 / 4 | |
| 1.2.42 | 5 / 4 | |
| 1.2.41 | 5 / 4 | |
| 1.2.40 | 5 / 4 | |
| 1.2.39 | 5 / 4 | |
| 1.2.38 | 5 / 4 | |
| 1.2.37 | 5 / 4 | |
| 1.2.36 | 5 / 4 | |
| 1.2.35 | 5 / 4 | |
| 1.2.34 | 5 / 4 | |
| 1.2.32 | 5 / 4 | |
| 1.2.31 | 5 / 4 | |
| 1.2.30 | 5 / 4 | |
| 1.2.29 | 5 / 4 | |
| 1.2.28 | 5 / 4 | |
| 1.2.27 | 5 / 4 | |
| 1.2.26 | 5 / 4 | |
| 1.2.25 | 5 / 4 | |
| 1.2.24 | 5 / 4 | |
| 1.2.23 | 5 / 4 | |
| 1.2.19 | 5 / 4 | |
| 1.2.18 | 5 / 4 | |
| 1.2.17 | 5 / 4 | |
| 1.2.16 | 5 / 4 | |
| 1.2.15 | 5 / 4 | |
| 1.2.13 | 5 / 4 | |
| 1.2.12 | 5 / 4 | |
| 1.2.11 | 5 / 4 | |
| 1.2.10 | 5 / 4 | |
| 1.2.9 | 5 / 4 | |
| 1.2.8 | 5 / 4 | |
| 1.2.7 | 5 / 4 | |
| 1.2.6 | 5 / 4 | |
| 1.2.5 | 5 / 4 | |
| 1.2.4 | 5 / 4 | |
| 1.2.3 | 5 / 4 | |
| 1.2.2 | 5 / 4 | |
| 1.2.1 | 5 / 4 |
v1.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.