←back to thread

Show HN: Pyscn – Python code quality analyzer for vibe coders

(github.com)
136 points d-yoda | 3 comments | 05 Oct 25 13:22 UTC | HN request time: 0.459s | source

Hi HN! I built pyscn for Python developers in the vibe coding era. If you're using Cursor, Claude, or ChatGPT to ship Python code fast, you know the feeling: features work, tests pass, but the codebase feels... messy.

Common vibe coding artifacts:

• Code duplication (from copy-pasted snippets)

• Dead code from quick iterations

• Over-engineered solutions for simple problems

• Inconsistent patterns across modules

pyscn performs structural analysis:

• APTED tree edit distance + LSH

• Control-Flow Graph (CFG) analysis

• Coupling Between Objects (CBO)

• Cyclomatic Complexity

Try it without installation:

  uvx pyscn analyze .          # Using uv (fastest)
  pipx run pyscn analyze .     # Using pipx
  (Or install: pip install pyscn)
Built with Go + tree-sitter. Happy to dive into the implementation details!
1. xrd ◴[05 Oct 25 15:33 UTC] No.45482303[source]▶
I absolutely love this. Tests and code coverage metrics are still important, but so easy to leave behind as you are running toward the vibe. This is a nice addition to the toolbox.
replies(2): >>45482369 #>>45482870 #
2. d-yoda ◴[05 Oct 25 15:39 UTC] No.45482369[source]▶
Thank you! I'll keep improving it more and more!
3. smoe ◴[05 Oct 25 16:27 UTC] No.45482870[source]▶
I’d argue that those kinds of automated tools are much more important much earlier in a project than they used to be.

Personally, I can deal with quite a lot of jank and a lack of tests or other quality control tools in the early stages, but LLMs get lost so quickly. It’s like onboarding someone new to the codebase every hour or so.

You want to put them into a feedback loop with something or someone that isn’t you.