A managed extension repository for your organisation.
Vetted Visual Studio Code extensions, security validation, and controlled delivery through a dedicated company portal.
Assessment, delivery, and adoption.
One managed service.
Choose an area to see how it fits within your company’s repository.
Know the release before it enters your repository.
Review the artifact, its dependencies, and the access it requires. Validation is tied to a specific package version and the assessment scope agreed with your organisation.
- Artifact
- Publisher, package identity, and distribution source
- Behaviour
- Workspace access, execution, and external connections
- Changes
- New dependencies and material release differences
Your company’s packages belong in your company’s environment.
Each onboarded organisation receives a dedicated portal. Package coverage, validation records, and release availability are scoped to the client’s requirements.
- Repository
- Company-specific package availability
- Records
- Release-specific validation information
- Access
- Provisioning arranged during company onboarding
Give each developer the right starting point.
Individual onboarding introduces the service and the organisation’s access arrangements. Developers receive guidance for their own company environment and software approval requirements.
- Introduction
- Individual confirmation through the rollout email
- Guidance
- Company-specific access and approval instructions
- Provisioning
- Dedicated portal details supplied during onboarding
Fit the repository to your approval process.
ExtDepot is supplied under a paid enterprise agreement. Service scope reflects the client’s developer population, package coverage, validation requirements, and operational responsibilities.
Enterprise service scope →Company approval stays with you.
Validation records support decisions. Your organisation retains approval authority and its existing operational controls.
Review context follows the release.
Package identity, version, and assessment scope remain part of the repository decision.
Repository content stays private.
Package listings and client records are available in the dedicated company environment.
Your portal details arrive through company onboarding.
Already received a rollout email? Reply “Send my guide” to receive your next steps.