← Home

@applitools/screenshoter

npm Repository Homepage
22
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

danielputermangearmamit.rokachroy.selaapplitools-adminapplitools-readonlyiasisappnoam.mendelarik-applitoolsyotammademdenis.styrtkyrylo.onufriievormedaclementbarryidosapplitoolsgofilordalex.burdeynyyronikar_applitoolsbenny.halberstadtgrayscale64fatihsolhan-applitoolsitaiz134dockermasteranandbagmarsergovapplitoolsfluxomni.iommilappnoam.gaashroeefranastasia.koifmanaretm_borodavkayonittzairilevyasundaram-applitoolsamir.groismanemasuarynaama.shohamadamcarmimulygottliebyoavnaveh-applitoolschaimaharonsonmovshonetta.bondyshirbinranhadardmytro-hrostyslav.pidburachynskyi.applitoolstaltool

Keywords

applitoolstest automationvisual regressionautomationtestingtestsscreenshots

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@applitools/image AI (dependencies): First-party Applitools package; consistent with the rest of the dependency set across all versions. ai
license uncommon-license:SEE LICENSE IN LICENSE AI (license): Standard Applitools license pattern used across their entire SDK suite. ai
provenance no-provenance AI (provenance): Applitools org consistently publishes without Sigstore provenance; stable pattern across all versions. ai

Versions (showing 22 of 22)

Version Deps Published
3.12.21 4 / 6
3.12.20 4 / 6
3.12.19 4 / 6
3.12.18 4 / 6
3.12.17 4 / 6
3.12.16 4 / 6
3.12.15 4 / 6
3.12.14 4 / 6
3.12.13 4 / 6
3.12.12 4 / 6
3.12.11 4 / 6
3.12.7 4 / 6
3.12.6 4 / 6
3.12.5 4 / 6
3.12.4 4 / 6
3.12.3 4 / 6
3.12.2 4 / 6
3.12.1 4 / 6
3.12.0 4 / 6
3.11.7 4 / 6
3.11.6 4 / 6
3.11.5 4 / 6

v3.12.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.14

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.12.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.11.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.11.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.11.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.