Tracking Dependencies

This guide walks through setting up end-to-end dependency tracking for a project.

Step 1: Create a Project

Navigate to Projects and create a new project. Use a name that matches the service or repository (e.g. "api-service", "web-frontend").

Step 2: Upload Your Manifest

The fastest path is uploading a manifest file:

1. Open the project you just created
2. Click Upload Manifest
3. Select your package.json, pyproject.toml, or other supported file
4. Review the detected dependencies

See Manifest Upload for supported formats.

Step 3: Review Detected Deprecations

After the manifest is processed, the project page will show any dependencies that have known deprecations. Review the urgency levels:

• Critical items need immediate attention
• Important items should be addressed in the current quarter
• Planned items can be scheduled for future sprints

Step 4: Subscribe to Categories

To stay informed as new deprecations are announced:

1. Go to Subscriptions
2. Subscribe to the categories that match your project's technology stack
3. Choose your preferred notification frequency

Step 5: Keep Manifests Updated

As your project evolves, re-upload your manifest periodically (or after significant dependency changes) to keep the tracking data current.

Tips

• One project per deployable — create separate projects for each service or application you maintain
• Review weekly — check your project dashboard at least once a week for new deprecations
• Prioritise by urgency — focus migration effort on critical and important items first