Ever joined a new repo and spent hours figuring out what goes where? This fixes that.

pip install codemappr

codemappr scan .

Detects 20+ project types purely from file patterns, maps your architecture, explains folder purposes, finds entry points — all fully offline. Outputs a rich terminal dashboard, committable Markdown report, and an interactive HTML report.

No API keys. No login. No internet. Just install and run.

Would love feedback on edge cases and project types you'd want added. V2 with a file relationship map is coming.

🔗 github.com/erensh27/CodeMappr

I've built a free online Maven download tool that helps developers download Maven JAR dependencies along with all their transitive dependencies as a single ZIP file.

Why I built this: I needed to regularly download Maven JARs and their transitive dependencies for my projects that has tons of dependencies and whenever I add a new feature and its dependencies change, I need to download newly added dependencies with their transitive dependencies. I used to use other tools (jar-download.com) but it is paid now, so I created a completely free, open-source alternative that doesn't store any data and works entirely client-side.

Live Demo: https://maven-tools.mohants.com/

GitHub: https://github.com/pmg1991/maven-tools

Features

Client-side dependency resolution : It happens entirely in your browser

Transitive dependency resolution : Automatically resolves all transitive dependencies including parent POMs

Version conflict resolution : Uses depth-based conflict resolution (shallowest depth wins) same as mvn

Dependency tree visualization : Displays hierarchical dependency tree with conflict information and direct download links

ZIP download : Download all resolved JARs as a single ZIP file

No data retention : Your XML is never stored - everything happens client-side

Netlify Edge Functions : Serverless proxy for Maven Central with streaming support

How It Works

1. Paste your Maven dependencies in XML format
2. Click "Resolve Jars" to resolve all transitive dependencies
3. View the dependency tree with direct download links
4. Click "Download All as ZIP" to download all resolved JARs

Use Cases

• Quickly download dependencies for offline development
• Bundle dependencies for deployment
• Analyze dependency trees and conflicts

The tool is completely free, open-source (MIT License), and doesn't store any of your data. Give it a try and let me know what you think!

Edit: fixed markdown first time posted something using markdown

https://i.redd.it/oip9cy23fr1h1.gif

DevHelper has grown so much in the past 5 years. From a simple tool that sits in your tray menu and lets you trigger urls and shell commands, throught a UI app addition and extensions to AI.
Now its more powerfull than ever. It your prototype development hotspot, where you have the controle over the AI not vice-versa. You start your idea with ai and plan mode, or by manually adding components. You need help of ai to speed things up, fire up any prompt, anything you can do manually you can do it with the AI, "add new screen", "add app bar", "change the image", "when i press the sign up button navigate to the new sign up screen" ... or you have a big idea in your head, type it in the plan mode, and let the AI build the design so you can refine it later, or go into the more powerfull interactive plan, where you build screen by screen, step by step, you dont like what AI is planing, refine the plan.

And at the end, when you are ready, with a click of a button generate a plan to build the real app, by first answering few questions to pick the tech-stack, and then with a single click let Codex generate the entire code bas for free. Dont like codex, would rather use someting else, you can download the entire plan.md with all the screenshots of everything you have desined in a single zip file, and use it wherever you want.

This is one of the features built in the DevHelper, and you have so much more, with so many more to come, but to keep this project alive for free, we need all the support we can get, either by donating via buymeacoffe, or spreding the word on the social media.

Get the latest version on our website

https://reddit.com/link/1tdp7vp/video/18tn12nx891h1/player

Download link:

https://smileytech.mk/devhelper

I am lazy when it comes to making changelogs and remember what I changed or noting down.

I have spent the last four days pouring blood and sweat into this, hope it works for you!

so I decided to just build DiffLogs. It's a changelog generator for specs. You can use YAML, JSON, Postman, GraphQL, or even just type what changed in plain English if you don't have a spec.

I am continue to update the website and make it better and looking for feedback on what else to add.

Still building, The roadmap includes Slack integration, email notifications, and API keys for CI/CD. and the ability to change the tone of voice in the changelog for your custom log.

Current features:

• Detects breaking changes automatically
• Shareable public changelog URLs
• Team collaboration with shared history
• Custom style instructions to match your tone

here is the website if you would like to check it out and give some feedback
https://www.difflogs.com

Hey , I've been researching how dev teams handle release notes and changelogs.

Most tools I've found (Beamer, Headway) require you to write everything manually. ReleaseNotes.io does some auto-generation but the output is one generic version for everyone.

Curious What tools are you using for this today?

What's missing from the current options?

Does your team produce different versions for customers vs internal teams?

Would love to hear what's working and what isn't.

Hey all, just looking for some idea roasting before starting to build.

Not selling anything. Want to know if this is wanted or if it's only me who wants it.

Problem: clients outgrowing Webflow but you can't trust them with a free 2D canvas. Webflow, Webstudio, Framer, all start from infinite freedom and are designer-first-oriented. Client breaks the site. Dev/designer gets called back.

A headless composable section layer (similar to what Relume does for Webflow, but for any framework): a curated catalog of pre-built section components (hero, features, footer, pricing, etc.) you import into any framework. Each section has multiple layout variants that share the same content slots, so layout swap never loses content. Themed via design tokens. Agent-friendly through MCP.

The idea on top:

- Visual editor installs into your framework project (Next, Astro, Nuxt, Vue+Vite). Not a hosted SaaS.

- Mounts at an /admin-style route in your own app, gated by your existing auth.

- Users compose pages from the catalog. No free positioning, no custom css/js, no classes, no anything that could break

- Edits write json files into your repo. Never an external DB

- Publish triggers a GitHub App commit, your CI/CD redeploys

- MIT open source. Pairs with any headless CMS for content

- Composer only writes .json. Your .tsx/.vue/.astro stays sovereign

Some questions:

- Would you install this into a client repo?

- "Only writes JSON, never code" as the round-trip-safety boundary, convincing or do you see holes?

- Anyone shipped TinaCMS / Plasmic / Decap to non-tech clients, what broke

- Any other issues you can see with this proposed approach?

Hey everyone,

I’ve been using AI assistants (Claude/Cursor) for a while, but I kept running into two annoying issues:

1. Package hallucinations: The AI suggests an import for a package I don’t even have in my package.json.
2. Version/Method hallucinations: It suggests a method like prisma.user.findFirstOrThrow() when I’m on an older version of Prisma where that doesn't exist yet.

To fix this, I built ctxai—a Model Context Protocol (MCP) server that makes the LLM "version-aware."

How it works:

It injects a "version fingerprint" of your actual environment into the AI’s context. Before the AI gives you a code snippet, it runs a validation layer to check if the code actually works with your installed versions.

The tools it adds to your AI:

• get_project_context: Scans your root and maps every installed package/version (Node & Python).
• validate_suggestion: A 3-layer validator that catches missing packages and hallucinated methods.
• get_package_docs: Fetches live metadata from npm/PyPI to help the AI self-correct.

Current Tech Stack Support:

• Node.js: Reads package.json and uses TypeScript definitions for method checks.
• Python: Reads requirements.txt/pyproject.toml and handles tricky import-to-pip name mappings (like PIL → Pillow).

I also included a benchmark suite of 28 test cases to ensure it’s actually catching errors without too many false positives.

I’m a student and still learning the ropes of MCP, so I’d love some feedback on the architecture or the validation logic!

GitHub: https://github.com/Nirvanjha2004/ctxAI-MCP-tool-to-reduce-hallucinations/tree/main

Would love to know: Are there any specific libraries where you find AI hallucinations to be the most frequent? I want to add more "mock API surfaces" to the benchmark.