@vendure/testing GPL-3.0-or-later 33 versions

@vendure/testing

npm Repository Homepage

End-to-end testing tools for Vendure projects

33

Versions

GPL-3.0-or-later

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

michaelbromleyvendure_teamdlhckhousein_is_programming

Keywords

venduretestinge2e

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): mime-types is a well-established, low-risk utility replacing form-data/node-fetch; not a suspicious addition.	ai	2026/07/01
maintainer-change	maintainer-added	AI (maintainer-change): vendure_team is the org's CI publisher; consistent with legitimate team account addition for this package.	ai	2026/06/02
dependencies	unvetted-dep:faker	AI (dependencies): faker is a standard test-data generation library; appropriate for a testing utilities package.	ai	2026/04/30
semgrep	semgrep:base64-decode	AI (semgrep): Decodes a hardcoded TEST_IMAGE_BASE_64 constant for test fixtures; not a payload risk.	ai	2026/04/29
phantom-deps	phantom-dep:sql.js	AI (phantom-deps): sql.js is declared as a runtime dep in package.json; phantom-dep heuristic is a false positive here.	ai	2026/04/29

Versions (showing 33 of 33)

Version	Deps	Published
3.7.1	7 / 9	2026-07-14
3.7.0	7 / 9	2026-07-01
3.6.4	8 / 9	2026-06-01
3.6.2	8 / 9	2026-04-13
3.6.1	8 / 9	2026-04-09
3.6.0	8 / 9	2026-03-31
3.5.7	8 / 9	2026-04-13
3.5.6	8 / 9	2026-03-30
3.5.3	8 / 9	2026-01-30
3.5.1	8 / 9	2025-11-14
3.4.0	8 / 9	2025-08-01
3.3.7	8 / 9	2025-07-18
3.3.3	8 / 9	2025-06-06
3.3.2	8 / 9	2025-05-28
3.1.8	8 / 9	2025-03-31
3.1.7	8 / 9	2025-03-06
3.1.6	8 / 9	2025-03-06
3.1.5	8 / 9	2025-03-06
3.1.4	8 / 9	2025-02-28
3.1.3	8 / 9	2025-02-14
3.1.2	8 / 9	2025-01-22
3.1.1	8 / 9	2024-12-17
3.1.0	8 / 9	2024-12-04
3.0.8	8 / 9	2024-12-03
3.0.7	8 / 9	2024-12-02
3.0.6	8 / 9	2024-11-15
3.0.5	8 / 9	2024-10-15
3.0.4	8 / 9	2024-10-04
3.0.3	8 / 9	2024-09-11
3.0.2	8 / 9	2024-09-10
3.0.1	8 / 9	2024-08-21
3.0.0	8 / 9	2024-07-17
2.3.4	8 / 9	2026-04-13

v3.7.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.7.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.3.7

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.8

1 finding

LOW No provenance attestation provenance

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

v3.1.7

1 finding

LOW No provenance attestation provenance

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

v3.1.6

1 finding

LOW No provenance attestation provenance

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

v3.1.5

1 finding

LOW No provenance attestation provenance

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

v3.1.4

1 finding

LOW No provenance attestation provenance

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

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.8

1 finding

LOW No provenance attestation provenance

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

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.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.