@x12i/ai-providers-router
Unified router for all LLM provider implementations
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@x12i/logxer | AI (dependencies): Same x12i publisher namespace with strong approval track record; stable sibling dependency. | ai | |
| dependencies | unvetted-dep:@x12i/ai-provider-openai | AI (dependencies): Same x12i publisher namespace with strong approval track record; stable sibling dependency. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): x12i publishes frequently in rapid succession as part of their normal release workflow; no malicious indicators present. | ai | |
| provenance | no-provenance | AI (provenance): Small internal package from a consistent publisher; lack of Sigstore attestation is not a blocking concern here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.9.2 | 7 / 2 | |
| 4.9.0 | 7 / 2 | |
| 4.8.12 | 7 / 2 | |
| 4.8.6 | 7 / 2 | |
| 4.8.0 | 7 / 2 | |
| 4.7.6 | 7 / 2 | |
| 4.6.2 | 7 / 2 | |
| 4.6.1 | 7 / 2 | |
| 4.6.0 | 7 / 2 |
v4.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.