resilient-llm

2025 was the year when we saw extreme impact of supply chain attack. npm did something last month to counter this by retiring old auth tokens in favor of a new authentication method they call trusted publishing, it uses OIDC to authenticate automated publishing via CI. but it seems like a rushed decision. poor coordination and incomplete docs. result: many package publishers are stuck and not able to release the updates to their package. It's not been two weeks and we already see almost 2k issues on github, the number will rise exponentially. * Search results on github : https://github.com/search?q=npm+trusted+publishing&type=issu... * the case in point: https://github.com/gitcommitshow/resilient-llm/issues/39 * Docs issue : https://github.com/npm/cli/issues/8884 * The bug : https://github.com/npm/cli/issues/8730

ResilientLLM is a minimalist but robust LLM integration layer designed to ensure reliable, seamless interactions across multiple LLM providers by intelligently handling failures and rate limits out-of-the-box. Available as a node.js package `npm i resilient-llm`, support for other languages coming soon. With just few lines of code, you can avoid writing and maintaining the code to deal with challenges such as: 1. Unstable network conditions 2. Intermittent errors and inconsistent error handling 3. Unpredictable LLM API rate limit errors More about the motivation and features in the README. Keen to hear your thoughts. If you like this, do star the repo and share your feature requests.