@kb-labs/adapters-kblabs-gateway
KB Labs Gateway LLM adapter — OpenAI-compatible with automatic JWT token refresh
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with strong track record; no CI provenance is a process gap, not a security signal for this package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 2.109.0 | 1 / 8 | |
| 2.107.0 | 1 / 8 | |
| 2.106.0 | 1 / 8 | |
| 2.105.0 | 1 / 8 | |
| 2.104.0 | 1 / 8 | |
| 2.103.0 | 1 / 8 | |
| 2.102.0 | 1 / 8 | |
| 2.101.0 | 1 / 8 | |
| 2.100.0 | 1 / 8 | |
| 2.98.0 | 1 / 8 | |
| 2.96.0 | 1 / 8 | |
| 2.94.0 | 1 / 8 | |
| 2.93.0 | 1 / 8 | |
| 2.89.0 | 1 / 8 | |
| 2.87.0 | 1 / 8 | |
| 2.77.0 | 1 / 8 | |
| 2.75.0 | 1 / 8 | |
| 2.69.0 | 1 / 8 | |
| 2.66.0 | 1 / 8 | |
| 2.61.0 | 1 / 8 | |
| 2.47.0 | 1 / 8 | |
| 2.45.0 | 1 / 8 | |
| 2.44.0 | 1 / 8 | |
| 2.43.0 | 1 / 8 | |
| 2.42.0 | 1 / 8 | |
| 2.38.0 | 1 / 8 | |
| 2.37.0 | 1 / 8 | |
| 2.36.0 | 1 / 8 | |
| 2.35.0 | 1 / 8 | |
| 2.30.0 | 1 / 8 | |
| 2.27.0 | 1 / 8 | |
| 2.22.0 | 1 / 8 | |
| 2.20.0 | 1 / 8 | |
| 2.19.0 | 1 / 8 | |
| 2.18.0 | 1 / 8 | |
| 2.17.0 | 1 / 8 | |
| 2.16.0 | 1 / 8 | |
| 2.13.0 | 1 / 8 | |
| 2.11.0 | 1 / 8 | |
| 2.9.0 | 1 / 8 | |
| 2.6.0 | 1 / 8 |
v2.109.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.107.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.103.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.