weaviate-client
JS/TS client for Weaviate
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual maintainer to GitHub Actions CI/CD publishing, confirmed by SLSA provenance attestation. Standard org practice. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a declared dependency used transitively via graphql-request; not a phantom dep. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 9 / 34 | |
| 3.12.1 | 9 / 34 | |
| 3.12.0 | 9 / 34 | |
| 3.11.0 | 9 / 34 | |
| 3.10.0 | 8 / 35 | |
| 3.9.0 | 8 / 35 | |
| 3.8.1 | 8 / 35 | |
| 3.8.0 | 8 / 35 | |
| 3.7.0 | 8 / 35 | |
| 3.6.2 | 8 / 35 | |
| 3.6.1 | 8 / 35 | |
| 3.6.0 | 8 / 35 | |
| 3.5.4 | 8 / 35 | |
| 3.5.3 | 8 / 35 | |
| 3.5.2 | 8 / 35 | |
| 3.5.1 | 8 / 35 | |
| 3.5.0 | 8 / 35 | |
| 3.4.2 | 8 / 35 | |
| 3.4.1 | 8 / 35 | |
| 3.4.0 | 8 / 35 | |
| 3.3.6 | 8 / 35 | |
| 3.3.4 | 8 / 35 | |
| 3.3.3 | 8 / 35 | |
| 3.3.2 | 8 / 35 | |
| 3.3.1 | 8 / 35 | |
| 3.3.0 | 8 / 35 | |
| 3.2.5 | 8 / 35 | |
| 3.2.4 | 6 / 39 | |
| 3.2.3 | 6 / 39 | |
| 3.2.2 | 6 / 38 | |
| 3.2.1 | 6 / 38 | |
| 3.2.0 | 6 / 38 | |
| 3.1.5 | 6 / 38 | |
| 3.1.4 | 6 / 38 | |
| 3.1.3 | 6 / 38 | |
| 3.1.2 | 6 / 38 | |
| 3.1.1 | 6 / 38 | |
| 3.1.0 | 6 / 38 | |
| 3.0.9 | 6 / 36 | |
| 3.0.8 | 6 / 36 | |
| 3.0.7 | 6 / 36 | |
| 3.0.6 | 6 / 36 | |
| 3.0.5 | 6 / 36 | |
| 3.0.4 | 6 / 36 | |
| 3.0.3 | 6 / 36 | |
| 3.0.2 | 6 / 36 | |
| 3.0.1 | 6 / 36 | |
| 3.0.0 | 6 / 36 | |
| 2.14.5 | 3 / 9 | |
| 2.14.4 | 3 / 9 | |
| 2.14.3 | 3 / 9 | |
| 2.14.2 | 3 / 7 | |
| 2.14.1 | 2 / 9 | |
| 2.14.0 | 2 / 8 | |
| 2.13.0 | 2 / 8 | |
| 2.12.1 | 2 / 8 | |
| 2.12.0 | 2 / 8 | |
| 2.11.1 | 2 / 8 | |
| 2.11.0 | 2 / 8 | |
| 2.10.1 | 2 / 8 | |
| 2.3.0 | 2 / 8 | |
| 2.2.0 | 2 / 8 | |
| 2.1.0 | 2 / 8 | |
| 2.0.0 | 2 / 8 | |
| 1.1.2 | 2 / 8 | |
| 1.1.1 | 2 / 8 | |
| 1.1.0 | 2 / 8 | |
| 1.0.0 | 2 / 2 | |
| 0.0.1 | 1 / 0 | |
| 3.12.0-alpha.0 | 9 / 34 | |
| 3.9.0-rc.0 | 8 / 35 | |
| 3.8.0-alpha.1 | 8 / 35 | |
| 3.8.0-alpha.0 | 8 / 35 |
v3.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. 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.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
3 findingsAll previous maintainers (semi-technologies) were replaced by new maintainers (weaviate-io, daniel-weaviate, weaviate-tommy, augustas-weaviate). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-05-13. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.