@applitools/dom-shared
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Applitools org maintainer rotation; publisher confirmed as known maintainer with strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Applitools org maintainer rotation; no code changes and known publisher context. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with internal Applitools tooling; no code changes and known publisher. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 0 / 2 | |
| 1.1.3 | 0 / 2 | |
| 1.1.2 | 0 / 2 | |
| 1.1.1 | 0 / 2 | |
| 1.1.0 | 0 / 2 |
v1.2.1
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 (movsho) than the most recent previously approved version (danielputerman) on 2026-05-26, but movsho 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.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.