@applitools/spec-driver-playwright
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): danielputerman is a long-standing Applitools team member with 404 approved packages; publisher change reflects internal org transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are consistent with Applitools internal team rotation, not an external takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removals paired with additions from same org; consistent with internal team restructuring. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.9.6 | 2 / 4 | |
| 1.9.5 | 2 / 4 | |
| 1.9.4 | 2 / 4 | |
| 1.9.3 | 2 / 4 | |
| 1.9.2 | 2 / 4 | |
| 1.9.1 | 2 / 4 | |
| 1.9.0 | 2 / 4 | |
| 1.8.5 | 2 / 4 | |
| 1.8.4 | 2 / 4 | |
| 1.8.3 | 2 / 4 | |
| 1.8.2 | 2 / 4 | |
| 1.8.1 | 2 / 4 | |
| 1.8.0 | 2 / 4 | |
| 1.7.10 | 2 / 4 | |
| 1.7.9 | 2 / 4 | |
| 1.7.8 | 2 / 4 | |
| 1.7.7 | 2 / 4 | |
| 1.7.6 | 2 / 4 | |
| 1.7.5 | 2 / 4 | |
| 1.7.4 | 2 / 4 | |
| 1.7.3 | 2 / 4 | |
| 1.7.2 | 2 / 4 | |
| 1.7.1 | 2 / 4 | |
| 1.7.0 | 2 / 4 | |
| 1.6.1 | 2 / 4 | |
| 1.6.0 | 2 / 4 | |
| 1.5.13 | 2 / 4 | |
| 1.5.12 | 2 / 4 | |
| 1.5.11 | 2 / 4 | |
| 1.5.10 | 2 / 4 | |
| 1.5.9 | 2 / 4 | |
| 1.5.8 | 2 / 4 | |
| 1.5.7 | 2 / 4 | |
| 1.5.6 | 2 / 4 | |
| 1.5.5 | 2 / 4 | |
| 1.5.4 | 2 / 4 | |
| 1.5.3 | 2 / 4 | |
| 1.5.2 | 2 / 4 | |
| 1.5.1 | 2 / 4 | |
| 1.5.0 | 2 / 4 | |
| 1.4.3 | 2 / 4 | |
| 1.4.2 | 2 / 4 | |
| 1.4.1 | 2 / 4 | |
| 1.4.0 | 2 / 4 | |
| 1.3.49 | 2 / 4 | |
| 1.3.48 | 2 / 4 | |
| 1.3.47 | 2 / 4 | |
| 1.3.46 | 2 / 4 | |
| 1.3.45 | 2 / 4 |
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.