← Home

@applitools/tunnel-client

npm Repository Homepage
51
Versions
SEE LICENSE IN LICENSE
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Established Applitools SDK package; missing description is a cosmetic issue, not a risk indicator. ai
dependencies unvetted-dep:@applitools/req AI (dependencies): Sibling Applitools monorepo package; unvetted status reflects review lag, not risk. ai
dependencies unvetted-dep:@applitools/utils AI (dependencies): Sibling Applitools monorepo package; unvetted status reflects review lag, not risk. ai
dependencies unvetted-dep:@applitools/logger AI (dependencies): Sibling Applitools monorepo package; unvetted status reflects review lag, not risk. ai
dependencies unvetted-dep:@applitools/socket AI (dependencies): Sibling Applitools monorepo package; unvetted status reflects review lag, not risk. ai
dependencies unvetted-dep:@applitools/execution-grid-tunnel AI (dependencies): Sibling Applitools monorepo package; unvetted status reflects review lag, not risk. ai

Versions (showing 51 of 65)

View all versions
Version Deps Published
1.12.2 8 / 10
1.12.1 8 / 10
1.12.0 8 / 10
1.11.14 8 / 10
1.11.13 8 / 10
1.11.12 7 / 9
1.11.11 7 / 9
1.11.10 7 / 9
1.11.9 7 / 9
1.11.8 7 / 9
1.11.7 7 / 9
1.11.6 7 / 9
1.11.5 7 / 9
1.11.4 7 / 9
1.11.3 7 / 9
1.11.2 7 / 9
1.11.1 7 / 9
1.11.0 7 / 9
1.10.4 7 / 9
1.10.3 7 / 9
1.10.2 7 / 9
1.10.1 7 / 9
1.10.0 7 / 9
1.9.1 7 / 9
1.9.0 7 / 9
1.8.1 7 / 8
1.8.0 7 / 8
1.7.0 7 / 8
1.6.7 7 / 8
1.6.6 7 / 8
1.6.5 7 / 4
1.6.4 7 / 4
1.6.3 7 / 4
1.6.2 7 / 4
1.6.1 7 / 4
1.6.0 7 / 4
1.5.11 7 / 4
1.5.10 7 / 4
1.5.9 7 / 4
1.5.8 7 / 4
1.5.7 7 / 4
1.5.6 7 / 4
1.5.5 7 / 4
1.5.4 7 / 4
1.5.3 7 / 4
1.5.2 7 / 4
1.5.1 7 / 4
1.5.0 7 / 4
1.4.1 7 / 4
1.4.0 7 / 4
1.3.2 7 / 4

v1.12.2

1 finding
LOW No provenance attestation provenance

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

v1.12.1

1 finding
LOW No provenance attestation provenance

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

v1.6.5

1 finding
LOW No provenance attestation provenance

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

v1.6.4

1 finding
LOW No provenance attestation provenance

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

v1.6.3

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.11

1 finding
LOW No provenance attestation provenance

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

v1.5.10

1 finding
LOW No provenance attestation provenance

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

v1.5.9

1 finding
LOW No provenance attestation provenance

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

v1.5.8

1 finding
LOW No provenance attestation provenance

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

v1.5.7

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: noam.gaash → applitools-admin (on 2024-06-27, known maintainer) provenance

This version was published by a different npm account (applitools-admin) than the most recent previously approved version (noam.gaash) on 2024-06-27, but applitools-admin 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.5.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: noam.gaash → applitools-admin (on 2024-06-16, known maintainer) provenance

This version was published by a different npm account (applitools-admin) than the most recent previously approved version (noam.gaash) on 2024-06-16, but applitools-admin 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.5.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: applitools-admin → noam.gaash (on 2024-06-16, known maintainer) provenance

This version was published by a different npm account (noam.gaash) than the most recent previously approved version (applitools-admin) on 2024-06-16, but noam.gaash 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.5.4

1 finding
LOW No provenance attestation provenance

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

v1.5.3

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.

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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