VersionTrack
VersionTrack - dependency updates in Slack
Dependency updates from multiple repositories in one clear report, directly in Slack.
Developer tool
About
VersionTrack brings npm dependency updates from selected GitHub repositories into one clear Slack report. Your team immediately sees which packages need attention, how large the change is and which project it affects, without opening every package.json by hand.
Why use it
- One shared priority list. Updates live in one clear view instead of scattered checks and manual notes.
- Decision-ready context. The report shows the package, repository, versions and change level, including major updates and deprecated packages.
- The team stays in control. VersionTrack informs the team. It never changes code or deploys an update without a decision.
- Limited access. The GitHub App uses read-only permissions and only the repositories chosen during installation.
How much time can it save
- 30 to 90 minutes each week. That is the time a team maintaining 10 repositories may spend gathering dependency-update information manually.
- About 2 to 6 hours per person each month. This is a realistic saving in that scenario because one Slack report replaces the discovery work.
- A transparent estimate. The tool saves review and prioritization time, not the engineering work needed to change code.
Who VersionTrack is for
- Node.js and TypeScript teams. Especially teams maintaining several GitHub applications or libraries.
- Technical leads and maintainers. People who need to assess update risk without opening every project manually.
- Quality and security owners. Teams that want to notice important updates and deprecations earlier.
Installation and first scan
- Select Add to Slack and install the app in the chosen workspace.
- Connect the GitHub App with only Metadata: Read-only and Contents: Read-only access.
- Choose the repositories that VersionTrack may access in GitHub.
- Open App Home in Slack, choose a reporting channel and set the monitored repositories.
- Run
/deps scanor use the scan button. Progress is posted to the channel and becomes the final report.
What a report contains
- Full context. The repository, package name, current and latest version, and change level: patch, minor or major.
- Useful actions in Slack. Filter one or more repositories, sort findings, reveal more items and export the current scan to a Markdown file.
Current scope
- GitHub: selected public and private repositories. VersionTrack does not require access to an entire organization.
- npm: analysis of
package.jsonandpackage-lock.json, version comparison and deprecation information. - Monorepos: basic detection of manifests in repository subdirectories.
- Slack: OAuth installation, App Home, manual and scheduled scans, and interactive reports in the chosen channel.
What VersionTrack does not do
In its first release, the tool does not modify code, create branches, open pull requests or install packages. It organizes updates while the team decides what to ship. Bitbucket and more package ecosystems are planned after the GitHub integration is stable.
Key Features
Multi-repository scans
One GitHub App installation can monitor selected projects of an organization or user.
Patch, minor and major
Semantic version changes are classified clearly, so major upgrades do not disappear among small patches.
Repository selection
Repositories can be selected and later enabled or disabled directly from Slack.
Reports and Markdown export
Filter a report by repositories, sort results and download the current scan as a Markdown file.
Live scan progress
A progress message shows completed repositories and checked packages, then becomes the final report.
Clear errors and deprecations
Missing manifests, access issues, API limits and deprecated packages are shown against the affected repository.
Privacy & Security
VersionTrack has only the access needed to read dependency manifests and publish its own reports.
