@slate-serializers/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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Used for CSS-in-JS style processing consistent with DOM serializer purpose. | ai | |
| phantom-deps | phantom-dep:postcss-js | AI (phantom-deps): Companion to postcss, same usage context. | ai | |
| typosquat | typosquat.levenshtein:jsdom | AI (typosquat): Scoped monorepo package; not a typosquat of jsdom. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped monorepo package; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped monorepo package; not a typosquat of koa. | ai | |
| phantom-deps | phantom-dep:css-select | AI (phantom-deps): Used transitively via htmlparser2/domutils; declared as direct dep per package description. | ai | |
| phantom-deps | phantom-dep:htmlparser2 | AI (phantom-deps): Core dependency per package description; referenced in config files is expected for this serializer. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped monorepo package; not a typosquat of zod. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped monorepo package; not a typosquat of got. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.5.4 | 8 / 0 | |
| 2.5.3 | 8 / 0 | |
| 2.5.2 | 8 / 0 | |
| 2.5.1 | 8 / 0 | |
| 2.5.0 | 8 / 0 | |
| 2.4.0 | 8 / 0 | |
| 2.2.3 | 8 / 0 | |
| 2.2.2 | 8 / 0 | |
| 2.2.1 | 8 / 0 | |
| 2.2.0 | 8 / 0 | |
| 2.1.6 | 11 / 0 | |
| 2.1.5 | 11 / 0 | |
| 2.1.4 | 11 / 0 | |
| 2.1.3 | 11 / 0 | |
| 2.1.2 | 11 / 0 | |
| 2.1.1 | 0 / 0 | |
| 2.1.0 | 11 / 0 | |
| 2.0.1 | 11 / 0 | |
| 2.0.0 | 11 / 0 |
v2.5.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (thompsonsj) on 2026-07-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.