They need to give your app the environment variables later so they cannot throw away the key.
For non-sensitive environment variables, they also show you the value in the dashboard so you can check and edit them later.
Things like 'NODE_ENV=production' vs 'NODE_ENV=development' is probably something the user wants to see, so that's another argument for letting the backend decrypt and display those values even ignoring the "running your app" part.
You're welcome to add an input that goes straight to '/dev/null' if you want, but it's not exactly a useful feature.
I'm not sure I follow. How does an integrity check help when the source is compromised? The developer doesn't know that their repo is compromised. They continue posting legitimate hashes because the repo is legitimately compromised.
I didn't see any complaints about any kind of artificial intelligence, research or otherwise, besides large language models, in this article.
Large language models are a single kind of AI, and a particularly annoying kind when you are forced to use them for deterministic or fact seeking tasks
or did you read the article? you're probably an LLM. why am I here? fuck this website
True but LLMs are all that are being sold right now. Mainly because people think they are intelligent because they're basically bullshit artist simulators.
I don't think the future of AI is with LLMs either. Not only LLMs anyway.