@gitlab/gitlab-ai-provider
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@anycable/core | AI (phantom-deps): Declared runtime dep used as optional WebSocket transport; referenced in config but not directly imported is expected for a multi-transport AI provider SDK. | ai | |
| phantom-deps | phantom-dep:vscode-jsonrpc | AI (phantom-deps): Declared runtime dep for JSON-RPC transport; phantom classification is expected for a multi-transport SDK where transports are conditionally used. | ai | |
| phantom-deps | phantom-dep:graphql-request | AI (phantom-deps): Declared runtime dep for GraphQL transport; phantom classification is expected for a multi-transport SDK. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Declared runtime dep for socket.io transport; phantom classification is expected for a multi-transport SDK. | ai | |
| provenance | no-provenance | AI (provenance): GitLab CI/CD published package; lack of Sigstore provenance is common and not a disqualifier given the verified @gitlab scope and consistent metadata. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 8 / 22 | |
| 4.0.0 | 8 / 22 | |
| 3.6.1 | 8 / 22 | |
| 3.6.0 | 8 / 22 | |
| 3.5.1 | 8 / 22 | |
| 3.5.0 | 8 / 22 | |
| 3.4.1 | 8 / 22 | |
| 3.4.0 | 8 / 22 | |
| 3.3.1 | 8 / 22 | |
| 3.3.0 | 8 / 22 | |
| 3.2.0 | 8 / 22 | |
| 3.1.3 | 7 / 22 | |
| 3.1.2 | 7 / 22 | |
| 3.1.1 | 7 / 22 | |
| 3.1.0 | 7 / 22 | |
| 3.0.9 | 7 / 22 | |
| 3.0.8 | 7 / 22 | |
| 3.0.7 | 7 / 22 | |
| 3.0.6 | 7 / 22 | |
| 1.0.5 | 7 / 22 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.