@wterm/dom
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA attestation present; missing gitHead is a cosmetic CI change, not a supply chain risk for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual publish to GitHub Actions CI/CD with SLSA attestation; consistent with vercel-labs org practices. | ai | |
| typosquat | typosquat.levenshtein:jsdom | AI (typosquat): @wterm/dom is a scoped terminal emulator package; Levenshtein match to 'jsdom' is a false positive on the short suffix 'dom'. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): @wterm/dom is a scoped terminal emulator package; Levenshtein match to 'koa' is a false positive on the short suffix 'dom'. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @wterm/dom is a scoped terminal emulator package; Levenshtein match to 'zod' is a false positive on the short suffix 'dom'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @wterm/dom is a scoped terminal emulator package; Levenshtein match to 'joi' is a false positive on the short suffix 'dom'. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @wterm/dom is a scoped terminal emulator package; Levenshtein match to 'got' is a false positive on the short suffix 'dom'. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 1 / 3 | |
| 0.2.1 | 1 / 3 | |
| 0.2.0 | 1 / 3 | |
| 0.1.9 | 1 / 3 | |
| 0.1.8 | 1 / 3 | |
| 0.1.7 | 1 / 2 | |
| 0.1.6 | 1 / 2 | |
| 0.1.5 | 1 / 2 | |
| 0.1.4 | 1 / 2 | |
| 0.1.3 | 1 / 2 | |
| 0.1.2 | 1 / 2 | |
| 0.1.1 | 1 / 2 | |
| 0.1.0 | 1 / 2 |
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ctate.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.