The latest articles on DEV Community by fixbeacon (@fixbeacondevs). https://dev.to/fixbeacondevs https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3873362%2F27bf744a-f045-472d-a180-5e8bbf3081e5.png https://dev.to/fixbeacondevs en fixbeacon Sat, 11 Apr 2026 10:54:02 +0000 https://dev.to/fixbeacondevs/fixbeacon-dependency-scans-that-stay-close-to-the-repo-3ae7 https://dev.to/fixbeacondevs/fixbeacon-dependency-scans-that-stay-close-to-the-repo-3ae7 <p>If you maintain real services, "we have Dependabot" is not the whole story. You still end up bouncing between PR noise, registries, advisories, and spreadsheets when you want a <strong>single place</strong> to answer: <em>what is exposed right now, how bad is it, and what should we do next?</em></p> <p>That gap is what we're building toward with <strong><a href="https://fixbeacon.dev/" rel="noopener noreferrer">FixBeacon</a></strong> — a dependency and vulnerability dashboard tied to the repositories you care about.</p> <h2> What you can try today </h2> <p>The app lives here: <strong><a href="https://app.fixbeacon.dev/" rel="noopener noreferrer">https://app.fixbeacon.dev/</a></strong></p> <p>In the current experience you can:</p> <ul> <li>Connect <strong>GitHub</strong> (and work with <strong>Azure DevOps</strong> flows where enabled in the product).</li> <li>Add repositories to a workspace and <strong>run scans</strong> from the dashboard.</li> <li>See <strong>severity breakdowns</strong>, <strong>installed packages</strong> (with vulnerable packages highlighted), and <strong>trend</strong> views over time.</li> <li>Open a <strong>detail panel</strong> for a finding with identifiers, ecosystem context, and <strong>update-oriented guidance</strong> when the data supports it (target version, notes links, and similar signals).</li> <li>Browse a <strong>public intelligence feed</strong> with ecosystem filters (for example <strong>NuGet</strong> and <strong>npm</strong>).</li> </ul> <p>The marketing site (positioning + updates) stays on <strong><a href="https://fixbeacon.dev/" rel="noopener noreferrer">https://fixbeacon.dev/</a></strong>.</p> <h2> Why I'm posting this on DEV </h2> <p>This is early software. The useful feedback is rarely "looks nice" — it's specifics:</p> <ul> <li>Which workflow broke first (connect, add repo, scan, navigation)?</li> <li>Which signal is <strong>missing</strong> (ecosystem, SBOM import, CI, policy, noise controls)?</li> <li>Which explanation would have saved you 20 minutes?</li> </ul> <p>If you try it on a repo you actually ship, tell me what felt misleading, slow, or incomplete. That kind of note changes the roadmap faster than any internal brainstorm.</p> <h2> A small ask </h2> <p>If this resonates, try the app and leave a comment here with:</p> <ol> <li>your ecosystem (npm / NuGet / polyglot),</li> <li>the first screen that confused you (if any),</li> <li>the one metric or export you'd need to recommend it to a teammate.</li> </ol> <p>Thanks for reading — and for any time you spend kicking the tires.</p> <p><em>Disclaimer: I'm building FixBeacon. Links: <a href="https://fixbeacon.dev/" rel="noopener noreferrer">fixbeacon.dev</a> · <a href="https://app.fixbeacon.dev/" rel="noopener noreferrer">app.fixbeacon.dev</a></em></p> security saas dotnet npm