@holochain/client — Greenflagged

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

zippy314zo-eljost-smatthmethetasinnerveesocallum.dunstermattyg

Keywords

holochainclientconductor api

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
license	uncommon-license:CAL-1.0	AI (license): CAL-1.0 is Holochain's long-standing license for this package.	ai	2026/07/27
maintainer-change	maintainer-added	AI (maintainer-change): Org-internal maintainer addition on long-standing legitimate project.	ai	2026/07/27
publish-pattern	new-deps-added	AI (publish-pattern): All new deps are mainstream, well-known libraries.	ai	2026/07/27
dependencies	unvetted-dep:@holochain/serialization	AI (dependencies): First-party Holochain Foundation package, not third-party unvetted code.	ai	2026/07/27
phantom-deps	phantom-dep:ws	AI (phantom-deps): Used via isomorphic-ws config, normal WebSocket dependency.	ai	2026/07/27
phantom-deps	phantom-dep:eslint-plugin-tsdoc	AI (phantom-deps): ESLint plugin misplaced in deps; benign dev tooling.	ai	2026/07/27
phantom-deps	phantom-dep:eslint-plugin-prettier	AI (phantom-deps): ESLint plugin misplaced in deps; benign dev tooling.	ai	2026/07/27
phantom-deps	phantom-dep:eslint-config-prettier	AI (phantom-deps): ESLint config misplaced in deps; benign dev tooling.	ai	2026/07/27
phantom-deps	phantom-dep:prettier	AI (phantom-deps): Lint/format tool misplaced in deps, not devDeps; benign dev tooling.	ai	2026/07/27

Versions (showing 42 of 42)

Version	Deps	Published
0.20.8	9 / 22	2026-07-21
0.20.7	9 / 22	2026-07-02
0.20.6	9 / 22	2026-06-30
0.20.5	9 / 22	2026-05-15
0.20.4	9 / 22	2026-05-13
0.20.2	9 / 22	2026-01-08
0.20.1	9 / 22	2025-12-05
0.20.0	9 / 19	2025-11-20
0.19.3	9 / 19	2025-09-05
0.19.2	9 / 19	2025-07-21
0.19.1	9 / 19	2025-06-30
0.19.0	9 / 19	2025-04-22
0.18.1	9 / 19	2025-03-11
0.18.0	9 / 19	2024-12-18
0.16.7	10 / 18	2023-11-29
0.12.5	8 / 18	2023-03-01
0.12.3	8 / 18	2023-02-24
0.12.0	8 / 18	2023-01-27
0.11.14	8 / 18	2023-01-19
0.11.13	8 / 16	2023-01-16
0.11.4	8 / 16	2022-12-21
0.10.4	5 / 16	2022-12-14
0.10.3	6 / 16	2022-12-12
0.10.2	6 / 16	2022-12-08
0.10.1	6 / 16	2022-12-08
0.10.0	10 / 16	2022-12-07
0.9.3	7 / 11	2022-11-03
0.9.2	7 / 11	2022-10-01
0.9.1	7 / 11	2022-10-01
0.9.0	7 / 11	2022-09-30
0.8.0	7 / 10	2022-08-24
0.7.0	7 / 10	2022-08-01
0.6.0	7 / 10	2022-07-08
0.5.0	7 / 10	2022-07-05
0.4.3	7 / 10	2022-06-28
0.4.2	7 / 10	2022-06-28
0.4.1	7 / 10	2022-06-15
0.4.0	7 / 10	2022-06-07
0.3.4	7 / 10	2022-06-07
0.3.2	3 / 10	2022-01-20
0.3.1	3 / 9	2022-01-14
0.3.0	3 / 9	2022-01-12

v0.20.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: thetasinner → callum.dunster (on 2026-07-21, known maintainer) provenance

This version was published by a different npm account (callum.dunster) than the most recent previously approved version (thetasinner) on 2026-07-21, but callum.dunster 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.

v0.20.7

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: veeso → thetasinner (on 2026-07-02, known maintainer) provenance

This version was published by a different npm account (thetasinner) than the most recent previously approved version (veeso) on 2026-07-02, but thetasinner 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.

v0.20.6

2 findings

HIGH Publisher changed: veeso → callum.dunster (on 2026-06-30) provenance

This version was published by a different npm account than previous versions on 2026-06-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.20.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: veeso → jost-s (on 2026-05-15, known maintainer) provenance

This version was published by a different npm account (jost-s) than the most recent previously approved version (veeso) on 2026-05-15, but jost-s 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.

v0.20.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: veeso → jost-s (on 2026-05-13, known maintainer) provenance

This version was published by a different npm account (jost-s) than the most recent previously approved version (veeso) on 2026-05-13, but jost-s 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.

v0.19.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.

v0.18.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.

v0.18.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.

v0.16.7

1 finding

LOW No provenance attestation provenance

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

v0.12.5

1 finding

LOW No provenance attestation provenance

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

v0.12.3

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.14

1 finding

LOW No provenance attestation provenance

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

v0.11.13

1 finding

LOW No provenance attestation provenance

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

v0.11.4

1 finding

LOW No provenance attestation provenance

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

v0.10.4

1 finding

LOW No provenance attestation provenance

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

v0.10.3

1 finding

LOW No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

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

v0.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.