Third-party dependency safety
An AI agent solved a date-handling bug in your TypeScript project by adding a dependency you've never heard of, `@temporal-utils/parse`, and the build is green. The fix is two lines and looks elegant. Before you merge a new third-party package the agent chose, how do you verify it's safe and appropriate?
Implement
audit_new_dependency(registry_names: list[str], candidate: str, weekly_downloads: int, days_since_publish: int, transitive_count: int, license_id: str) → list[str]Examples
in
[["left-pad","date-fns","lodash"],"date-fns",12000000,30,3,"MIT"]out[]in
[["left-pad","date-fns"],"@temporal-utils/parse",500,20,2,"MIT"]out["not-in-registry"]in
[["parse-ms","tiny-date"],"tiny-date",800,900,42,"GPL-3.0"]out["large-transitive-tree","low-adoption","restricted-license","unmaintained"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 15 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.