@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, 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-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 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 0 / 2 | |
| 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 | |
| 1.0.16 | 0 / 2 | |
| 1.0.15 | 0 / 2 | |
| 1.0.14 | 0 / 2 |
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.