Dependency Nightshift
Reads overnight CVE feeds and tells you which ones can actually reach your code. Built for Quiet Hours — build an agent that does useful work while its user is asleep. CVE matching against the dependency tree. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Dependency Nightshift — main view
Dependency Nightshift — result state
On the clock
What shipped, what didn't
Completed in time
CVE matching against the dependency tree.
Unfinished / faked
Reachability analysis is shallow — direct imports only.
Obstacles
The first approach needed a background worker I didn't have time to deploy, so I moved it inline at minute 14.
Lessons learned
Writing the submission summary first would have caught the scope problem earlier.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Dependency Nightshift data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
The idea is strong and the execution is most of the way there. The demo path broke once, which is what separates this from the top three today.
Hana Kobayashi
Principal Research Engineer, Independent
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
Claudia Reyes
Staff Engineer, Vantage Analytics
Nice work under the clock. The unfinished list is longer than the finished one, but what shipped works and you were straight about it.
Discussion
0 comments
No comments yet.