← Home

@applitools/image

npm Repository Homepage
24
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by Applitools SDK monorepo release cadence; no malicious payload found in this or surrounding versions. ai
dependencies unvetted-dep:png-async AI (dependencies): Image-processing dependency consistent with package purpose; stable across versions. ai
dependencies unvetted-dep:bmpimagejs AI (dependencies): BMP image library consistent with package purpose; stable across versions. ai
dependencies unvetted-dep:@applitools/logger AI (dependencies): Internal Applitools logger dep; same publisher org, stable across versions. ai

Versions (showing 24 of 24)

Version Deps Published
1.2.13 7 / 5
1.2.12 7 / 5
1.2.11 7 / 5
1.2.10 7 / 5
1.2.9 7 / 5
1.2.8 7 / 5
1.2.7 7 / 5
1.2.6 5 / 5
1.2.5 5 / 5
1.2.4 5 / 5
1.2.3 5 / 5
1.2.2 5 / 5
1.2.1 5 / 5
1.2.0 5 / 5
1.1.21 5 / 5
1.1.20 5 / 5
1.1.19 5 / 5
1.1.18 5 / 5
1.1.17 5 / 5
1.1.16 5 / 5
1.1.15 5 / 5
1.1.14 5 / 5
1.1.13 5 / 5
1.1.12 5 / 5

v1.2.13

1 finding
LOW No provenance attestation provenance

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

v1.1.20

1 finding
LOW No provenance attestation provenance

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

v1.1.19

1 finding
LOW No provenance attestation provenance

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

v1.1.18

1 finding
LOW No provenance attestation provenance

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

v1.1.17

1 finding
LOW No provenance attestation provenance

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

v1.1.16

1 finding
LOW No provenance attestation provenance

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

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

v1.1.14

1 finding
LOW No provenance attestation provenance

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

v1.1.13

1 finding
LOW No provenance attestation provenance

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

v1.1.12

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.