Dependency Signal Monitor
Pricing
Pay per usage
Reads your repo's dependency manifests through a GitHub connector, scores each dependency for abandonment risk, and opens an issue listing the ones that are dying.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Abhishek Khanra
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
Your authorized GitHub MCP connector. The Actor reads your dependency manifests through it and opens the results issue through the same connection. Your token never reaches the Actor: Apify injects it server-side.
GitHub username or organization that owns the repository to analyse.
The repository whose dependencies you want checked. It does not have to be one you own: public repositories are readable by any token.
Branch to read manifests from. Leave blank for the repository default.
Files to read. Leave empty to auto-detect the standard manifests at the repository root.
[]Dev dependencies rarely ship to production but a dead build tool still blocks you.
Caps the run. Signals are fetched per dependency, so this is the main cost control.
Maintenance option. Not shown in the form.
Leave blank to use the analysed repository's owner. Set this when you are monitoring a repository you do not own and want the report filed in your own tracker.
Leave blank to file the issue in the repository that was analysed.
Health runs 0 to 100, where 100 is healthy. Anything at or below this lands in the issue.
On by default. The Actor scores everything and writes the dataset, but does not touch your repository. Turn this off once the output looks right.