Developer and Vendor Dependency Checklist

Check access, ownership records, documentation and recovery dependencies before a supplier changes. Review the heuristic score and evidence-based action list.

✓ Published Method ✓ Reviewed 16 October 2026 ✓ Explicit Assumptions
🔒

Privacy First: All calculations happen in your browser. No data is sent to any server. Your answers stay on your device.

If your solo developer quit, your dev shop went out of business, or your agency relationship ended badly—would your business survive?

Most founders think "my developer/agency is reliable" is a good answer. It's not.

Solo developers quit. Agencies go out of business. Dev shops get acquired. Relationships end. People get sick, win lotteries, get better offers—or yes, get hit by buses.

And when they do, founders discover they don't have access to servers. Can't access their code. Don't know where backups are. Can't even log into the domain registrar. Worse: their infrastructure is hosted in the agency's AWS account—they don't own it.

This 5-minute assessment shows you exactly where you're vulnerable—before it's too late.

  • ✓ Find critical access gaps (servers, code, domains)
  • ✓ Identify single points of failure
  • ✓ Get a prioritized action plan
  • ✓ Download a PDF report to share

Checklist limits: Scores summarize self-reported access and continuity gaps. They are not validated incident probabilities or a legal ownership assessment.

Do You Have These Risks?

Most founders don't realize they have critical dependencies until it's too late. These guides help you spot the warning signs:

Common Questions

Why review dependencies when I trust my developer or agency?
Continuity depends on authorized alternate access and usable recovery procedures. Trusted people and suppliers can become unavailable. Review account access, knowledge sharing and restoration evidence without assuming misconduct.
Does working with an agency automatically create more risk than a solo developer?
No. Risk depends on access, contractual rights, operational practices, knowledge distribution and tested recovery. An agency can provide broader coverage, while a poorly structured arrangement can still leave important dependencies.
Does having repository access mean I own the code?
Repository access and intellectual property ownership are different. Ownership and licenses depend on jurisdiction, employment or supplier agreements, assignments and third-party terms. Verify both authorized access and relevant rights with qualified advice where needed.
What does the score mean?
It is the rounded mean of ten self-reported editorial answer values from 0 to 100. Higher values mean more reported dependency gaps. It is not a validated probability of disruption or an audit result. Review critical gaps individually.
What should I do when access or recovery is uncertain?
Identify the business owner for each account, establish appropriate alternate access, record secure credential locations, review contracts and test a representative deployment and restore. Prioritize actual risk rather than trying only to improve the aggregate score.

Infrastructure Risk Assessment

of questions

Your Infrastructure Risk Assessment

Dependency Gap Index

Want Help Reducing Your Risk?

Schedule a free 15-minute consultation to discuss your specific situation.

Schedule Free Consultation

A trusted supplier can become unavailable. Check whether the business can administer its accounts, obtain its source and data, and operate recovery procedures without relying on one person or company.

What to verify

  • Authorized business access to hosting, identity, repositories, domains, DNS, backups and billing.
  • Contracts, intellectual property assignments, licenses and usable export rights. Ownership depends on jurisdiction and agreements. Creating an account or paying a bill does not settle every legal question.
  • Current architecture and deployment records, secure credential handling, restoration evidence and named operational owners.
  • Handover procedures, alternate administrators and reviewed permissions when people leave.

Use a password manager or secrets system. Document where credentials are held and how authorized recovery works rather than collecting passwords in a general spreadsheet.

Scoring method and limits

Each of 10 answers has an editorial gap value from 0 to 100, shown in the tool’s source. The result is the arithmetic mean, rounded: sum / 10. If every answer is 50, the index is 50. Higher means more reported dependency gaps.

This is an unvalidated self-assessment, not the probability of disruption, a breach statistic or an audit. Critical account access and recovery gaps deserve attention even with a low aggregate. The PDF summarizes the same questionnaire and recommendations, not independently verified evidence.

No supported population rate establishes that 70% of businesses are disrupted by a supplier departure or that 89% of former contractors retain access. These claims and unrelated breach cost figures have been removed.

For next steps, review website handover and ownership and test whether another authorized operator can deploy and restore a representative service.

Sources

NIST CSF 2.0 provides outcomes for governing and managing cybersecurity risk. This short checklist is not a NIST assessment or certification. CISA Cross-Sector Cybersecurity Performance Goals address asset management, access control and recovery practices. Neither supplies the scoring weights or verifies your contractual rights.

Method and factual claims reviewed 16 October 2026. Sources support the principles described, not the example inputs or this tool’s scoring weights.