@washingtonpost/wpds-ui-kit
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Known maintainer alias publishing consistently; no takeover indicators in diff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived official package; dormancy explained by normal release cadence, no malicious diff. | ai | |
| phantom-deps | phantom-dep:@react-types/combobox | AI (phantom-deps): Used in config/type refs, not a real risk. | ai |
v2.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (subs-npm-builder) than the most recent previously approved version (davisshaver) on 2026-03-25, but subs-npm-builder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.