@lix-js/sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
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): Growth from bundled sqlite-wasm binary and shipped src/test files, not injected payload. | ai | |
| phantom-deps | phantom-dep:@lix-js/server-protocol-schema | AI (phantom-deps): Same-org scope dependency, not directly imported but expected. | ai | |
| source-diff | net-exec-file:dist/wasm/lix_js_sdk.js | AI (source-diff): wasm-bindgen generated glue, not a dropper; benign for this package. | ai | |
| provenance | missing-githead | AI (provenance): gitHead dropped due to CI/CD publish env change; SLSA attestation present. | ai | |
| provenance | publisher-changed | AI (provenance): Manual→CI/CD SLSA-attested transition, provenance IMPROVED. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): jco/wasm-bindgen build output for this WASM SDK; stable artifact type. | ai | |
| phantom-deps | phantom-dep:dedent | AI (phantom-deps): dedent is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 3 / 5 | |
| 0.8.1 | 3 / 5 | |
| 0.8.0 | 3 / 5 | |
| 0.7.0 | 1 / 3 | |
| 0.6.2 | 0 / 3 | |
| 0.6.1 | 0 / 3 | |
| 0.6.0 | 0 / 3 | |
| 0.5.1 | 8 / 10 | |
| 0.5.0 | 8 / 10 | |
| 0.4.10 | 7 / 10 | |
| 0.4.9 | 7 / 10 | |
| 0.4.8 | 7 / 10 | |
| 0.4.7 | 7 / 10 | |
| 0.4.6 | 7 / 10 | |
| 0.4.5 | 7 / 10 | |
| 0.4.4 | 7 / 10 | |
| 0.4.3 | 7 / 10 | |
| 0.4.2 | 7 / 10 | |
| 0.4.1 | 7 / 10 | |
| 0.4.0 | 7 / 10 | |
| 0.3.5 | 7 / 9 | |
| 0.3.4 | 7 / 9 | |
| 0.3.3 | 7 / 9 | |
| 0.3.2 | 7 / 9 | |
| 0.3.1 | 6 / 10 | |
| 0.3.0 | 6 / 10 | |
| 0.2.0 | 6 / 10 | |
| 0.1.0 | 7 / 10 | |
| 0.0.1 | 7 / 10 |
v0.8.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.8.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.8.0
5 findingsPackage contains compiled binaries that could be backdoors: • dist/jco/js-component-bindgen-component.core.wasm • dist/jco/js-component-bindgen-component.core2.wasm
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-10. This could indicate a legitimate maintainer transition or an account compromise.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samuelstroschein) than the most recent previously approved version (inlangbot) on 2025-01-31, but samuelstroschein 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.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samuelstroschein) than the most recent previously approved version (inlangbot) on 2025-01-17, but samuelstroschein 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.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (inlangbot) than the most recent previously approved version (samuelstroschein) on 2025-01-09, but inlangbot 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.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.