← Home

@applitools/dom-capture

npm Homepage
31
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
npm-metadata url-dep:cssom AI (npm-metadata): SHA-pinned devDependency only; not shipped to consumers. Stable pattern for this package's test tooling. ai
phantom-deps phantom-dep:@applitools/dom-shared AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic is unreliable for monorepo packages. ai

Versions (showing 31 of 31)

Version Deps Published
11.8.4 2 / 30
11.8.3 2 / 30
11.8.2 2 / 30
11.8.0 2 / 28
11.7.1 2 / 26
11.7.0 2 / 26
11.6.13 2 / 26
11.6.12 2 / 26
11.6.11 2 / 26
11.6.10 2 / 26
11.6.9 2 / 26
11.6.8 2 / 26
11.6.7 2 / 26
11.6.6 2 / 26
11.6.5 2 / 26
11.6.4 2 / 26
11.6.3 2 / 26
11.6.2 2 / 26
11.6.1 2 / 26
11.6.0 2 / 26
11.5.6 2 / 26
11.5.5 2 / 26
11.5.4 2 / 26
11.5.3 2 / 26
11.5.2 2 / 26
11.5.1 2 / 26
11.5.0 2 / 26
11.4.0 2 / 26
11.3.1 2 / 26
11.3.0 2 / 26
11.2.8 2 / 26

v11.8.4

1 finding
LOW No provenance attestation provenance

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

v11.8.3

1 finding
LOW No provenance attestation provenance

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

v11.5.5

1 finding
LOW No provenance attestation provenance

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

v11.5.4

1 finding
LOW No provenance attestation provenance

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

v11.5.3

1 finding
LOW No provenance attestation provenance

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

v11.5.2

1 finding
LOW No provenance attestation provenance

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

v11.5.1

1 finding
LOW No provenance attestation provenance

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

v11.5.0

1 finding
LOW No provenance attestation provenance

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

v11.4.0

1 finding
LOW No provenance attestation provenance

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

v11.3.1

1 finding
LOW No provenance attestation provenance

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

v11.3.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.

v11.2.8

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.