← Home

@applitools/spec-driver-puppeteer

npm Repository Homepage
48
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

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

Keywords

puppeteerchrome devtools protocolcdpdevtoolsapplitoolsautomationtestingtests

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Applitools monorepo package; missing description is a stable pattern across their packages. ai
provenance no-provenance AI (provenance): Established Applitools package; no provenance is consistent across their published versions. ai

Versions (showing 48 of 48)

Version Deps Published
1.8.6 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.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.10 2 / 4
1.6.9 2 / 4
1.6.8 2 / 4
1.6.6 2 / 4
1.6.5 2 / 4
1.6.4 2 / 4
1.6.3 2 / 4
1.6.2 2 / 4
1.6.1 2 / 4
1.6.0 2 / 4
1.5.1 2 / 4
1.5.0 2 / 4
1.4.30 2 / 4
1.4.29 2 / 4
1.4.28 2 / 4
1.4.27 2 / 4
1.4.26 2 / 4
1.4.25 2 / 4
1.4.24 2 / 4
1.4.23 2 / 4
1.4.22 2 / 4
1.4.21 2 / 4
1.4.20 2 / 4
1.4.19 2 / 4
1.4.18 2 / 4
1.4.17 2 / 4
1.4.16 2 / 4
1.4.15 2 / 4
1.4.14 2 / 4
1.4.13 2 / 4
1.4.12 2 / 4
1.4.11 2 / 4
1.4.10 2 / 4
1.4.9 2 / 4
1.4.8 2 / 4

v1.8.6

1 finding
INFO No provenance attestation provenance

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

v1.8.5

1 finding
INFO No provenance attestation provenance

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

v1.4.30

1 finding
INFO No provenance attestation provenance

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

v1.4.29

1 finding
INFO No provenance attestation provenance

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

v1.4.28

1 finding
INFO No provenance attestation provenance

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

v1.4.27

1 finding
INFO No provenance attestation provenance

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

v1.4.26

1 finding
INFO No provenance attestation provenance

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

v1.4.25

1 finding
INFO No provenance attestation provenance

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

v1.4.24

1 finding
INFO No provenance attestation provenance

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

v1.4.23

1 finding
INFO No provenance attestation provenance

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

v1.4.22

1 finding
INFO No provenance attestation provenance

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

v1.4.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.

v1.4.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.

v1.4.19

1 finding
INFO No provenance attestation provenance

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

v1.4.18

1 finding
INFO No provenance attestation provenance

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

v1.4.17

1 finding
INFO No provenance attestation provenance

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

v1.4.16

1 finding
INFO No provenance attestation provenance

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

v1.4.15

1 finding
INFO No provenance attestation provenance

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

v1.4.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.

v1.4.13

1 finding
INFO No provenance attestation provenance

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

v1.4.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.

v1.4.11

1 finding
INFO No provenance attestation provenance

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

v1.4.10

1 finding
INFO No provenance attestation provenance

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

v1.4.9

1 finding
INFO No provenance attestation provenance

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

v1.4.8

1 finding
INFO No provenance attestation provenance

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