@conduit-client/test SEE LICENSE IN LICENSE.txt 39 versions

@conduit-client/test

npm Repository Homepage

Luvio Next test utilities

39

Versions

SEE LICENSE IN LICENSE.txt

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

scarrawaysflwc-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:jest	AI (typosquat): Scoped @conduit-client package in Salesforce monorepo; not a typosquat of jest.	ai	2026/05/02
typosquat	typosquat.levenshtein:next	AI (typosquat): Scoped @conduit-client package in Salesforce monorepo; not a typosquat of next.	ai	2026/05/02
typosquat	typosquat.levenshtein:vitest	AI (typosquat): Scoped @conduit-client package in Salesforce monorepo; not a typosquat of vitest.	ai	2026/05/02

Versions (showing 39 of 39)

Version	Deps	Published
3.20.5	9 / 0	2026-05-27
3.20.4	9 / 0	2026-05-26
3.20.3	9 / 0	2026-05-21
3.20.0	9 / 0	2026-05-14
3.19.6	9 / 0	2026-05-11
3.19.5	9 / 0	2026-05-07
3.19.4	9 / 0	2026-04-29
3.19.3	9 / 0	2026-04-22
3.19.2	9 / 0	2026-04-10
3.19.1	9 / 0	2026-04-09
3.19.0	9 / 0	2026-04-08
3.18.0	9 / 0	2026-03-23
3.17.3	9 / 0	2026-03-12
3.17.2	9 / 0	2026-03-12
3.17.1	9 / 0	2026-03-10
3.17.0	9 / 0	2026-03-06
3.16.0	9 / 0	2026-03-04
3.15.1	9 / 0	2026-02-25
3.15.0	9 / 0	2026-02-25
3.14.0	9 / 0	2026-02-12
3.13.1	9 / 0	2026-02-11
3.13.0	9 / 0	2026-02-06
3.12.0	9 / 0	2026-02-04
3.11.0	9 / 0	2026-02-04
3.10.0	9 / 0	2026-01-29
3.9.0	9 / 0	2026-01-22
3.8.0	9 / 0	2026-01-14
3.7.1	9 / 0	2026-01-07
3.7.0	9 / 0	2025-12-19
3.6.3	9 / 0	2025-12-18
3.6.2	9 / 0	2025-12-18
3.6.1	9 / 0	2025-12-17
3.5.0	9 / 0	2025-12-08
3.4.0	9 / 0	2025-12-03
3.3.0	9 / 0	2025-11-21
3.2.0	9 / 0	2025-11-18
3.0.0	9 / 0	2025-11-17
2.1.0	9 / 0	2025-11-14
2.0.1	9 / 0	2025-11-04

v3.20.5

1 finding

LOW No provenance attestation provenance

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

v3.20.4

1 finding

LOW No provenance attestation provenance

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

v3.20.3

1 finding

LOW No provenance attestation provenance

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

v3.20.0

1 finding

LOW No provenance attestation provenance

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

v3.19.6

1 finding

LOW No provenance attestation provenance

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

v3.19.5

1 finding

LOW No provenance attestation provenance

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

v3.19.4

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@conduit-client/test' is 1 edit(s) away from popular package 'jest'.

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.

v3.19.3

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@conduit-client/test' is 1 edit(s) away from popular package 'jest'.

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.

v3.19.2

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@conduit-client/test' is 1 edit(s) away from popular package 'jest'.

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.

v3.19.1

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@conduit-client/test' is 1 edit(s) away from popular package 'jest'.

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.

v3.19.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@conduit-client/test' is 1 edit(s) away from popular package 'jest'.

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.

v3.18.0

1 finding

LOW No provenance attestation provenance

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

v3.17.3

1 finding

LOW No provenance attestation provenance

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

v3.17.2

1 finding

LOW No provenance attestation provenance

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

v3.17.1

1 finding

LOW No provenance attestation provenance

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

v3.17.0

1 finding

LOW No provenance attestation provenance

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

v3.16.0

1 finding

LOW No provenance attestation provenance

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

v3.15.1

1 finding

LOW No provenance attestation provenance

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

v3.15.0

1 finding

LOW No provenance attestation provenance

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

v3.14.0

1 finding

LOW No provenance attestation provenance

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

v3.13.1

1 finding

LOW No provenance attestation provenance

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

v3.13.0

1 finding

LOW No provenance attestation provenance

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

v3.12.0

1 finding

LOW No provenance attestation provenance

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

v3.11.0

1 finding

LOW No provenance attestation provenance

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

v3.10.0

1 finding

LOW No provenance attestation provenance

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

v3.9.0

1 finding

LOW No provenance attestation provenance

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

v3.8.0

1 finding

LOW No provenance attestation provenance

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

v3.7.1

1 finding

LOW No provenance attestation provenance

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

v3.7.0

1 finding

LOW No provenance attestation provenance

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

v3.6.3

1 finding

LOW No provenance attestation provenance

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

v3.6.2

1 finding

LOW No provenance attestation provenance

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

v3.6.1

1 finding

LOW No provenance attestation provenance

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

v3.5.0

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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

v2.0.1

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.