Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by jerrygoyal on Wednesday March 25, 2026 @02:57AM
(#47514164)
I don't think syntax is correct for pnpm
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by postalcoder on Wednesday March 25, 2026 @03:24AM
(#47514326)
Works for me?
$ pnpm add -D [email protected]
ERR_PNPM_NO_MATURE_MATCHING_VERSION No matching version found for [email protected] published by Wed Mar 18 2026..
You could also set the config this way: pnpm config set minimumReleaseAge 10080 --global
You may be thinking about the project-specific config, which uses YAML.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by exyi on Wednesday March 25, 2026 @05:30AM
(#47515136)
Do you know if there is override this specifically when I want to install a security patch? UV just claims that package doesn't exist if I ask for new version
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by postalcoder on Wednesday March 25, 2026 @05:43AM
(#47515225)
Yes there is. You can use those configs as flags in the CLI to override the global config.
eg:
npm install <package> --min-release-age 0
pnpm add <package> --minimum-release-age 0
uv add <package> --exclude-newer "0 days"
bun add <package> --minimum-release-age 0
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by collinmanderson on Thursday March 26, 2026 @02:30PM
(#47534015)
uv also has --exclude-newer-package which I think can be used for overriding just a certain package.
https://docs.astral.sh/uv/reference/cli/#uv-run--exclude-new... https://docs.astral.sh/uv/reference/settings/#exclude-newer-...
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by nikisweeting on Tuesday April 07, 2026 @05:28PM
(#47681583)
Note pnpm does not have this flag yet, please upvote this issue if you want it added: https://github.com/pnpm/pnpm/issues/11224
Currently pnpm only supports setting this option via persistent config file, not per-run.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by tomtomtom777 on Wednesday March 25, 2026 @09:58AM
(#47517429)
I understand that this is a good idea but it does feel really weird. Add a min-release-age to see if anyone who doesn't gets bitten.
Next up, we're going to advise a minimum-release-age of 14 days, cause most other projects use 7 days.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by bonoboTP on Wednesday March 25, 2026 @11:53AM
(#47519072)
You don't have to outrun the bear, just the other guy.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by zar1048576 on Thursday March 26, 2026 @07:22PM
(#47537145)
Wouldn't this just be a case of the bear catching one guy and then catching the other guy (especially if the issue was unnoticed altogether after the set number of days)?
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by talkin on Wednesday March 25, 2026 @02:37PM
(#47521393)
There will always be early adopters.
And maybe more importantly: security tools and researchers.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by zar1048576 on Thursday March 26, 2026 @07:21PM
(#47537134)
The minimum-release-age heuristic is certainly helpful as it theoretically gives the community a chance to identify the issue. Of course, in practice, these things aren't scanned or analyzed the way they should ideally be, which is a deeper issue. Pinning has definitely saved me on more than one occasion, but it doesn't strike at the root of the issue.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by montag on Tuesday March 31, 2026 @03:49AM
(#47584029)
Well this was prescient... https://news.ycombinator.com/item?id=47582220
I updated my global configs to set min release age to 7 days: