Codeac

📅 𝐍𝐞𝐱𝐭 𝐖𝐞𝐝𝐧𝐞𝐬𝐝𝐚𝐲: 𝐓𝐡𝐞 𝐓𝐲𝐩𝐞𝐒𝐜𝐫𝐢𝐩𝐭 𝐔𝐩𝐠𝐫𝐚𝐝𝐞

A quick heads-up: on April 29th, Codeac officially transitions its default TypeScript analysis to ESLint.

If you haven’t manually set your linter in .codeac.yml yet, here’s the breakdown:
⏳ 𝐂𝐮𝐫𝐫𝐞𝐧𝐭 𝐬𝐭𝐚𝐭𝐞: TSLint is still running.
✅ 𝐍𝐞𝐱𝐭 𝐰𝐞𝐞𝐤: We automatically level you up to ESLint for better security and modern syntax support.
🛡️ 𝐘𝐨𝐮𝐫 𝐨𝐰𝐧 𝐜𝐨𝐧𝐟𝐢𝐠? No action needed as your settings always come first.

Read the full blog post for all the details, migration tips, and a link to our quick Config Generator! 👇

https://www.codeac.io/blog/upcoming-changes-in-default-typescript-analysis.html

Upcoming changes in default TypeScript analysis | Codeac Starting April 29th, Codeac is updating its default TypeScript analysis from TSLint to ESLint. This change aligns our platform with current industry standards, ensuring better support for modern syntax and security rules.

𝐌𝐨𝐯𝐢𝐧𝐠 𝐭𝐨 𝐄𝐒𝐋𝐢𝐧𝐭: 𝐒𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐟𝐢𝐫𝐬𝐭, 𝐚𝐥𝐰𝐚𝐲𝐬 🛡️

Starting April 29th, Codeac is updating its default TypeScript analysis from TSLint to ESLint.

Why now? We intentionally kept our defaults untouched for years to give you a stable environment while you planned your transition. Now that the ESLint ecosystem is fully mature, we’re making the switch to ensure you benefit from:
✅ 𝐌𝐨𝐝𝐞𝐫𝐧 𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬: Full support for the latest TypeScript syntax.
✅ 𝐄𝐱𝐭𝐞𝐧𝐝𝐞𝐝 𝐑𝐮𝐥𝐞𝐬: Access to a vast library of security plugins.
✅ 𝐓𝐨𝐭𝐚𝐥 𝐒𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲: Alignment with the official industry roadmap.

We’ve designed this to be seamless. If you have your own config, nothing changes. For everyone else, we’re leveling up your code quality automatically.

Full details are here: https://www.codeac.io/blog/upcoming-changes-in-default-typescript-analysis.html

Upcoming changes in default TypeScript analysis | Codeac Starting April 29th, Codeac is updating its default TypeScript analysis from TSLint to ESLint. This change aligns our platform with current industry standards, ensuring better support for modern syntax and security rules.

Your Docker image might be bigger than it needs to be. 🐳

When installing Python dependencies inside a container, pip stores downloaded packages in its cache, which makes perfect sense on a local machine.

But inside Docker?

Image layers already provide caching. Keeping the pip cache only increases image size without adding value.

In production, that means:
• Larger images
• Slower pulls
• Longer deployments
• Bigger attack surface

Smaller images. Faster deployments. Cleaner builds.

Are you disabling pip cache in your Dockerfiles?

𝐒𝐭𝐨𝐩 𝐦𝐚𝐧𝐮𝐚𝐥𝐥𝐲 𝐟𝐢𝐱𝐢𝐧𝐠 𝐫𝐞𝐩𝐞𝐭𝐢𝐭𝐢𝐯𝐞 𝐢𝐬𝐬𝐮𝐞𝐬. 𝐋𝐞𝐭 𝐀𝐮𝐭𝐨𝐟𝐢𝐱 𝐝𝐨 𝐭𝐡𝐞 𝐡𝐞𝐚𝐯𝐲 𝐥𝐢𝐟𝐭𝐢𝐧𝐠! ⚡️

We are excited to introduce 𝐂𝐨𝐝𝐞𝐚𝐜 𝐀𝐮𝐭𝐨𝐟𝐢𝐱, a new way to bridge the gap between issue detection and resolution.

Keeping your codebase healthy shouldn't slow you down. With Autofix, you can now generate ready-to-review Pull Requests with suggested fixes directly from Codeac: no context-switching, no manual edits, just seamless improvements.

Currently available for JavaScript and TypeScript, with more languages coming!

Read the full announcement on our blog: https://www.codeac.io/blog/from-detection-to-resolution-in-no-time-introducing-autofix.html

𝐌𝐢𝐬𝐬𝐢𝐧𝐠 𝐉𝐢𝐧𝐣𝐚𝟐 𝐚𝐮𝐭𝐨𝐞𝐬𝐜𝐚𝐩𝐢𝐧𝐠 = 𝐬𝐢𝐥𝐞𝐧𝐭 𝐗𝐒𝐒 𝐫𝐢𝐬𝐤 🚨

Jinja2 does 𝐧𝐨𝐭 enable autoescaping by default.
That means user input rendered in templates can turn into a Cross-Site Scripting (XSS) vulnerability without you realizing it.

The fix is simple:
✅ Enable autoescaping explicitly
✅ Apply it to HTML, HTM, and XML templates
✅ Prevent untrusted input from becoming executable code

Codeac helps catch these issues early, before they reach production.

Quality vs. speed is an eternal tension in software development.

Developers push for maintainability, and the business pushes for delivery. Both are right.

Sometimes, shipping fast is necessary. But revisiting and refining the codebase to meet team standards is what makes that speed sustainable.

In the long run, neither speed nor quality should be an afterthought. The best outcomes come from intentionally balancing both. 🚀

Read more on our blog: https://www.codeac.io/blog/quality-or-speed-that-is-the-question.html

Quality or Speed - That is the Question | Codeac Balancing quality and speed in software development is a persistent challenge. This post delves into strategies to meet the needs of both developers and managers, ensuring rapid delivery without compromising on standards.

Loading the new year… ⏳✨

Wishing you calm days, smooth PRs, and plenty of green checks along the way.

We’re glad to be part of your journey.

Cheers to a great year ahead!

We can’t fix all holiday bugs, but we’re glad Codeac could help fix some in your code this year. 🐞

Thanks to everyone using Codeac this year, and to the team making it happen.

Happy holidays! 🎄

🎄 For the third year in a row, our team got together to visit the Christmas market. It's a tradition that has naturally become something we all look forward to each year.

It was a great opportunity to spend time together outside of work, enjoy the festive atmosphere, share good conversations, and enjoy great food along the way.

Moments like these remind us that what we’re building isn’t just a company, but a team. We’re grateful for the time spent together and excited to continue this tradition in the years to come.

Shadow variable declarations are a subtle but common source of confusion in codebases.

When a local variable uses the same name as one in an outer scope, it shadows the original, making the global value inaccessible and the code harder to read.

Clear naming and avoiding shadowing keep your code predictable, maintainable, and easier for others (and future you!) to understand.