@latimer-woods-tech/llm
LLM failover orchestration across Factory AI providers.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 2 / 9 | |
| 0.4.3 | 2 / 9 | |
| 0.4.2 | 2 / 9 | |
| 0.4.1 | 2 / 9 | |
| 0.2.0 | 2 / 9 |
v0.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.