HN user
I think Prawduct addresses a real problem. Claude Code builds what you ask for, not what you need, and the drift/inconsistency over a session is where most quality breaks down. The automatic /critic and /janitor skills are the strongest idea here making review happen by default rather than on-demand is the right design IMO.
Nice system but quick question: how does this compare to something like Semgrep? Semgrep also does tree sitter based pattern matching and has taint tracking now. Is the main difference the rule engine, performance, or something else? Always interested in more options in this space but the "open source SAST" field is getting crowded.
Every P1 post mortem I’ve been part of over the years usually ended with that we should’ve had monitoring for that. I looked for a solution that could surface those gaps across our entire stack but couldn’t find one, so I built it.
Cova scans your environment and identifies monitoring gaps before the next incident hits. It integrates with tools like Pagerduty, Datadog, Grafana, Sentry, Newrelic ect.. and audits your configs automatically. Each finding comes with a severity, a suggested fix, and a coverage score so you can clearly see where you’re exposed.
Beyond the audit, it can generate and deploy fixes to your tools in one click, scan repos (Github/Gitlab) to find unmonitored endpoints, investigate live incidents by pulling data across connected tools, and even flag new endpoints in PRs before they ship.
Tech stack I used: FastAPI + React, with Claude for the AI layer.
I also put together a demo on the landing page, just click “Enter Demo” to explore with sample data (no signup required). If you want to try the full capabilities, let me know and I can give you elevated access on the free tier. AMA!
Screenreading is a smart way to solve the integration problem. Every other tool in this space makes you connect each app one by one and you're always waiting for them to support your workflow. This just watches what you watch. Feels obvious in hindsight - cool stuff
Fun idea. The rarity based XP system is a good way to keep people motivated beyond the first few common sightings. Another idea could be seasonal bonuses like for example extra XP for migratory species that are only in your region for a few weeks.
Pretty cool concept - tried it out and it played really smoothly. The idea of navigating music by year + vibe instead of genre makes a lot of sense. Well done!
Cool project. Beyond cocktails, I could see something like this being useful for people who want to monitor their alcohol intake before driving - pour tracking that keeps a running count and warns you when you're approaching your limit. The "proactive intervention" model fits that perfectly.
This is the kind of thing that feels obvious but apparently still needs to be said. I've seen businesses run entirely off an Instagram page, and when the algorithm changes or the account gets flagged, they lose everything overnight. No way to reach their customers, no archive of their work, nothing.
Voltage glitching attacks are pretty brutal to defend against because you're essentially fighting physics, not software. You can write perfect code and still get bypassed by someone manipulating the electrical signals at the right microsecond..
The part about green getting 58.7% weight in the luminance calculation is one of those details that seems arbitrary until you realize it's literally modeled on the density of cone cells in the human retina. The whole algorithm is basically a map of what human eyes can't see.
I've wasted so many hours keeping API schemas and ORM models in sync on FastAPI projects.. how does it handle schema evolution on larger projects? Like if I rename a field or split a model into 2, does makemigrations detect that correctly or does it treat it as a drop + create?
Pretty cool, one thing that would be useful: some kind of alerting or watch feature. Like "notify me if this repo's health score drops below X" or if a dependency gets a CVE. Would make it useful for teams that maintain a lot of open source dependencies.