Mastodawn

GitHub Hit by Internal Repo Breach via Malicious VS Code Extension

GitHub's internal repositories were breached after a malicious Visual Studio Code extension was used to launch the attack, but thankfully, customer data appears to be safe. The incident has left users wondering what else may have been compromised.

https://osintsights.com/github-hit-by-internal-repo-breach-via-malicious-vs-code-extension?utm_source=mastodon&utm_medium=social

#MaliciousVsCodeExtension #Github #InternalRepoBreach #DeveloperTooling #EmergingThreats

GitHub Hit by Internal Repo Breach via Malicious VS Code Extension

GitHub reveals internal repo breach via malicious VS Code extension, learn how the attack happened and what you can do to protect yourself now.

OSINTSights

Paul Shryock Jan 1

What is the best HTML formatter that folks use in 2026?

Don't say prettier. It turns void elements into self-closing tags, which do not exist in HTML, so it produces invalid HTML.

See https://developer.mozilla.org/en-US/docs/Glossary/Void_element#self-closing_tags

I'm looking for an HTML formatter that produces valid HTML.

#Html #DeveloperTooling #SoftwareEngineering

Void element - Glossary | MDN

A void element is an element in HTML that cannot have any child nodes (i.e., nested elements or text nodes). Void elements only have a start tag; end tags must not be specified for void elements.

MDN Web Docs

Benedikt Ritter (he/him)Nov 15, 2025

🚨 New blog post: Packaging kotlin-lsp for NixVim

In this short how-to I show how to write a Nix derivation to package kotlin-lsp for use in a NixVim configuration. I also explain a little bit how I approach packaging Java applications with Nix, when I can't build them from source.

https://britter.dev/blog/2025/11/15/kotlin-lsp-nixvim/

#kotlin #java #nix #nixos #neovim #nixvim #developertooling #developerproductivity

Packaging kotlin-lsp for NixVim

A short how-to explaining how to package the kotlin-lsp language server with Nix in order to use it with NixVim

Issy Long Aug 10, 2025

Am I imagining a `git commit --fixup` helper tool that, given a staged change in a hunk of a file present in a previous commit, will automatically find that commit and `--fixup` that commit?

I'm fed up of noticing a problem, then `git log --oneline` and then copypasta a SHA and then `git rebase -i`, and then I notice another thing that's bad and the process starts over.

#Git #SoftwareDevelopment #DeveloperTooling #DevEx