@zilliz/milvus2-sdk-node
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate migration from human publisher to GitHub Actions CI/CD with SLSA provenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with transition to CI/CD publishing for this established @zilliz-scoped package. | ai | |
| dependencies | unvetted-dep:@dsnp/parquetjs | AI (dependencies): Long-standing dependency in this SDK; no malicious signals; stable across versions. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 10 / 11 | |
| 3.0.1 | 10 / 11 | |
| 3.0.0 | 10 / 11 | |
| 2.6.16 | 10 / 11 | |
| 2.6.15 | 10 / 11 | |
| 2.6.14 | 10 / 11 | |
| 2.6.13 | 10 / 11 | |
| 2.6.12 | 10 / 11 | |
| 2.6.11 | 9 / 10 | |
| 2.6.10 | 9 / 10 | |
| 2.6.9 | 9 / 10 | |
| 2.6.8 | 9 / 10 | |
| 2.6.7 | 9 / 10 | |
| 2.6.6 | 9 / 10 | |
| 2.6.5 | 9 / 10 | |
| 2.6.4 | 9 / 10 | |
| 2.6.3 | 9 / 10 | |
| 2.6.2 | 9 / 10 | |
| 2.6.1 | 9 / 10 | |
| 2.6.0 | 9 / 10 | |
| 2.5.13 | 9 / 10 | |
| 2.5.12 | 9 / 10 | |
| 2.5.11 | 9 / 10 | |
| 2.5.10 | 9 / 10 | |
| 2.5.9 | 9 / 10 | |
| 2.5.8 | 9 / 10 | |
| 2.5.7 | 9 / 10 | |
| 2.5.6 | 9 / 10 | |
| 2.5.5 | 9 / 10 | |
| 2.5.4 | 8 / 10 | |
| 2.5.3 | 8 / 10 | |
| 2.5.2 | 8 / 10 | |
| 2.5.1 | 8 / 10 | |
| 2.5.0 | 8 / 10 | |
| 2.4.11 | 8 / 10 | |
| 2.4.10 | 8 / 10 | |
| 2.4.9 | 8 / 10 | |
| 2.4.8 | 8 / 10 | |
| 2.4.7 | 8 / 10 | |
| 2.4.6 | 8 / 10 | |
| 2.4.5 | 8 / 10 | |
| 2.4.4 | 8 / 10 | |
| 2.4.3 | 8 / 10 |
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.