@applitools/req
Applitools fetch-based request library
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Expected from ncc bundling all deps into dist/cjs output. | ai | |
| source-diff | net-exec-file:dist/cjs/875.index.cjs.js | AI (source-diff): ncc-bundled webpack chunk with config/fs helpers, not a dropper; matches documented build:cjs pipeline. | ai | |
| dependencies | unvetted-dep:@applitools/types | AI (dependencies): First-party Applitools scoped package, same monorepo/publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @applitools/types, not third-party supply chain risk. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Bundled undici llhttp WASM binary; stable across versions of this package. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): License file exists in repo; standard Applitools SDK pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; provenance adoption is still rare. | ai | |
| dependencies | unvetted-dep:@applitools/logger | AI (dependencies): Same-org Applitools dependency; consistent pattern across all package versions. | ai | |
| dependencies | unvetted-dep:@applitools/utils | AI (dependencies): Same-org Applitools dependency; consistent pattern across all package versions. | ai | |
| phantom-deps | phantom-dep:@applitools/logger | AI (phantom-deps): Same-org dependency; likely used transitively or conditionally — stable false positive for this package. | ai |
Versions (showing 51 of 100)
| Version | Deps | Published |
|---|---|---|
| 1.11.2 | 4 / 8 | |
| 1.11.1 | 4 / 8 | |
| 1.11.0 | 5 / 7 | |
| 1.10.2 | 5 / 7 | |
| 1.10.1 | 5 / 7 | |
| 1.10.0 | 5 / 7 | |
| 1.9.3 | 5 / 7 | |
| 1.9.2 | 5 / 7 | |
| 1.9.1 | 5 / 7 | |
| 1.9.0 | 5 / 7 | |
| 1.8.8 | 5 / 7 | |
| 1.8.7 | 5 / 7 | |
| 1.8.6 | 5 / 7 | |
| 1.8.5 | 5 / 7 | |
| 1.8.4 | 5 / 7 | |
| 1.8.3 | 5 / 7 | |
| 1.8.2 | 5 / 7 | |
| 1.8.1 | 5 / 7 | |
| 1.8.0 | 5 / 7 | |
| 1.7.15 | 5 / 7 | |
| 1.7.14 | 5 / 7 | |
| 1.7.13 | 5 / 7 | |
| 1.7.12 | 5 / 7 | |
| 1.7.11 | 5 / 7 | |
| 1.7.10 | 5 / 7 | |
| 1.7.9 | 5 / 7 | |
| 1.7.8 | 5 / 7 | |
| 1.7.7 | 5 / 7 | |
| 1.7.6 | 5 / 7 | |
| 1.7.5 | 5 / 7 | |
| 1.7.4 | 5 / 7 | |
| 1.7.3 | 5 / 7 | |
| 1.7.2 | 5 / 7 | |
| 1.7.1 | 5 / 7 | |
| 1.7.0 | 5 / 7 | |
| 1.6.7 | 5 / 7 | |
| 1.6.6 | 5 / 7 | |
| 1.6.5 | 5 / 7 | |
| 1.6.4 | 5 / 7 | |
| 1.6.3 | 5 / 7 | |
| 1.6.2 | 5 / 7 | |
| 1.6.1 | 5 / 7 | |
| 1.6.0 | 5 / 6 | |
| 1.5.4 | 5 / 6 | |
| 1.5.3 | 5 / 6 | |
| 1.5.2 | 5 / 6 | |
| 1.5.1 | 5 / 6 | |
| 1.5.0 | 5 / 6 | |
| 1.4.0 | 5 / 6 | |
| 1.3.3 | 5 / 4 | |
| 1.3.2 | 5 / 4 |
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (noam.gaash) than the most recent previously approved version (applitools-admin) on 2025-04-13, 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.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.