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): Config-referenced optional integration; stable for this provider package. | ai | |
| phantom-deps | phantom-dep:vscode-jsonrpc | AI (phantom-deps): Config-referenced optional integration; stable for this provider package. | ai | |
| phantom-deps | phantom-dep:graphql-request | AI (phantom-deps): Config-referenced optional integration; stable for this provider package. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Config-referenced optional integration; stable for this provider package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 6.9.3 | 8 / 22 | |
| 6.9.2 | 8 / 22 | |
| 6.9.1 | 8 / 22 | |
| 6.9.0 | 8 / 22 | |
| 6.8.0 | 8 / 22 | |
| 6.7.1 | 8 / 22 | |
| 6.7.0 | 8 / 22 | |
| 6.6.0 | 8 / 22 | |
| 6.5.0 | 8 / 22 | |
| 6.4.2 | 8 / 22 | |
| 6.4.1 | 8 / 22 | |
| 6.4.0 | 8 / 22 | |
| 6.3.0 | 8 / 22 | |
| 6.2.1 | 8 / 22 | |
| 6.2.0 | 8 / 22 | |
| 6.1.1 | 8 / 22 | |
| 6.1.0 | 8 / 22 | |
| 6.0.0 | 8 / 22 | |
| 5.3.3 | 8 / 22 | |
| 5.3.2 | 8 / 22 | |
| 5.3.1 | 8 / 22 | |
| 5.3.0 | 8 / 22 | |
| 5.2.2 | 8 / 22 | |
| 5.2.1 | 8 / 22 | |
| 5.2.0 | 8 / 22 | |
| 5.1.2 | 8 / 22 | |
| 5.1.1 | 8 / 22 | |
| 5.1.0 | 8 / 22 | |
| 5.0.0 | 8 / 22 |
v6.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.