@percy/dom
Serializes a document's DOM into a DOM string suitable for re-rendering.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): @percy/dom is a legitimate scoped package; Levenshtein match to 'koa' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @percy/dom is a legitimate scoped package; Levenshtein match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:jsdom | AI (typosquat): @percy/dom is a legitimate scoped package; Levenshtein match to 'jsdom' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @percy/dom is a legitimate scoped package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @percy/dom is a legitimate scoped package; Levenshtein match to 'zod' is a false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.31.14 | 0 / 1 | |
| 1.31.13 | 0 / 1 | |
| 1.31.12 | 0 / 1 | |
| 1.31.11 | 0 / 1 | |
| 1.31.10 | 0 / 1 | |
| 1.31.9 | 0 / 1 | |
| 1.31.8 | 0 / 1 | |
| 1.31.7 | 0 / 1 | |
| 1.31.6 | 0 / 1 | |
| 1.31.5 | 0 / 1 | |
| 1.31.4 | 0 / 1 | |
| 1.31.3 | 0 / 1 | |
| 1.31.2 | 0 / 1 | |
| 1.31.1 | 0 / 1 | |
| 1.31.0 | 0 / 1 | |
| 1.30.11 | 0 / 1 |
v1.31.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.