probe-droid

To assess GitHub repository onboarding gaps for Endor Labs monitored-branch coverage, compare your GitHub repository inventory against Endor project details, GitHub App coverage, package evidence, and scan setup evidence to identify missing configurations.

Endor Labs monitored-branch coverage is the tracking of repository branches for security and dependency analysis. You need to evaluate it when onboarding GitHub repositories to ensure package manager integration, scan profiles, and reachability evidence are properly configured.

Yes, you need both GitHub and Endor API access to check repository onboarding readiness. This access allows the assessment tool to retrieve GitHub inventory and Endor project details to compare package, scan, and reachability evidence.

Yes, you can identify missing GitHub App coverage and package manager evidence without modifying source code. The assessment returns human-readable setup actions required for optimal onboarding without mutating source, GitHub, or Endor state.

The best way to find setup actions for Endor Labs scan profiles is to probe your GitHub organization for onboarding gaps. This comparison returns specific setup prescriptions for scan profiles, package managers, and reachability evidence.

Your Endor Labs coverage assessment shows missing reachability evidence when GitHub repositories lack the necessary scan setup configurations. Comparing GitHub inventory with Endor project details identifies these gaps and returns the required setup actions.