Hey devs ๐
I've been building the Python Teaching Assistant โ an open-source, beginner-friendly console program that teaches Python through conversation and real-life analogies, not textbook walls of text.
This week, two important things landed:
Code of Conduct
We made it official: no judgment, no gatekeeping. Whether someone's confused about indentation or submitting their first PR, they're welcome here. The CoC covers everything from respectful disagreement to how we handle reports โ privately, fairly, and seriously.
Security tooling
โ Bandit โ runs static analysis on the Python codebase, catches security anti-patterns automatically.
โ Dependency Review โ every pull request now gets scanned for known-vulnerable or deprecated packages.
Why does a teaching project need this? Because students copy patterns. If the code they learn from has security smells, those habits travel with them. We want to model good practice, not just explain it.
If you want to contribute, learn from the source, or just poke around โ the repo is open and the community is genuinely kind.
Drop questions in the comments โ through the security setup or the CoC approach.

Top comments (0)