A4Intermediate

Dependency Map

45 minEach new project

Format: List all external dependencies of your project and assess each dependency's risk.

Steps:

  1. Open any one of your projects (or imagine one)

  2. List all external dependencies:

    • Third-party services (Supabase, Vercel, Stripe, Claude API...)
    • npm packages (How many? Do you know what they all do?)
    • API integrations (Google Maps, SendGrid...)
  3. For each dependency, fill in:

Dependency name: _____
Purpose: _____
If it disappeared tomorrow:
  - What happens to my app? (Completely unusable? Partial functionality affected?)
  - What's the alternative?
  - How long to switch to the alternative?
Risk level: High / Medium / Low
  1. Draw a dependency graph — which dependencies depend on other dependencies?

Self-Assessment Criteria:

  • Are there any "single points of failure"? (One service goes down, the entire app goes down)
  • Are there any "hidden dependencies"? (Dependency chains you don't know about)
  • Do your critical dependencies have alternatives?

Self-Assessment Criteria

0/3

What You Will Learn

Platform risk awareness — you're building on someone else's platform, and they can change the rules at any time.

My Notes