Build an evidence-backed inventory of direct, transitive, runtime, development, and container dependencies.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this before judging age or security risk.
Find every package manifest and lockfile in scope. Include workspace roots, plugins, examples that ship, container base images, build actions, and language runtime pins. Prefer installed or locked versions over ranges in manifests.
For each item record:
Do not merge packages that share a name across ecosystems. Flag duplicate major versions, unlocked production dependencies, stale generated lockfiles, and manifests with no matching lockfile. If a scanner and lockfile disagree, show both and name the check needed to settle it.
Return a table, an evidence-gap list, and totals by ecosystem and use. Never infer that a package runs in production only because it appears in a manifest. Do not call the inventory complete while a deployable service or image remains unchecked.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.