Release notes

Endor Labs helps you select, secure, and maintain dependencies, so development moves fast and supply chain risk remains low. The following release notes highlight the most recent major capabilities and any major bug fixes published by Endor Labs.

We are excited to introduce the latest features and enhancements in Endor Labs.

Endor Labs now supports exporting scan data to an Amazon S3 storage bucket for archival, compliance, or integration with other tools. The S3 exporter supports exporting findings in JSON or SARIF format.

For more information, see Export findings to S3.

You can now use the None (Notify for each Finding) aggregation type to send separate notifications for every finding generated from the configured action policy, making it easier to track and assign individual security issues. This aggregation type is supported only for SAST and Secrets action policies.

For more information, see Aggregation types for notifications.

Endor Labs now includes finding tags and categories in the SARIF output when exporting findings to GitHub Advanced Security (GHAS). You can use these tags to filter and identify specific types of findings in GitHub code scanning, such as reachable vulnerabilities, findings with available fixes, or findings by category, like SCA, SAST, and Secrets.

For more information, see Filter findings by tags in GitHub.

We are excited to introduce the latest features and enhancements in Endor Labs.

The Endor Labs MCP server is now available in Developer Edition. You can get started without any prior configuration or Endor Labs account.

The Endor Labs MNP server Enterprise Edition has also been updated to provide easier configuration and setup.

For more information, see Endor Labs MCP server.

The Endor Labs MCP server is now available as a Gemini extension. You can use natural language commands to interact with the MCP server. For more information, see Endor Labs MCP server as a Gemini extension.

You can now use the Endor Labs GitHub Enterprise Server App to continuously monitor repositories on your GitHub Enterprise Server (GHES) instances and gain visibility into security and operational risks.

  • Continuously monitor repositories hosted in your GitHub Enterprise Server instance for risk and compliance.
  • Scan repositories for Software Composition Analysis (SCA), secrets, and Static Application Security Testing (SAST).
  • Scan pull requests and receive automated PR comments to assist with secure code reviews.
  • Offer flexible deployment options through both Endor Labs’ cloud scanning and on-premises scanning with Outpost.

For more information, see Deploy Endor Labs GitHub Enterprise App.

You can now view all notifications associated with a finding in the findings table, making it easier to access Jira tickets and other notification details.

For more information, see View all findings.

The dependency graph now offers improved rendering performance and enhanced node interactions, making it easier to visualize and explore complex dependency trees.

For more information, see View dependency graph.

Endor Labs now supports scanning Python projects that use UV by resolving dependencies from the pyproject.toml and uv.lock files.

For more information, see Scan Python projects.

You can now authenticate to Endor Labs by running the endorctl init command without specifying further details. When you run the command, the browser window opens, where you can select your authentication provider from the available options and complete the authentication process.

For more information, see endorctl init command.

We are excited to introduce the latest features and enhancements in Endor Labs.

You can now scan merge requests using the Endor Labs GitLab App. You can also configure MR comments to receive comments on your merge requests.

For more information, see GitLab App MR scans.

You can now enable urgent notifications in Endor Labs to receive real-time alerts for newly discovered malware, allowing you to take immediate action.

For more information, see Urgent Notifications.

Endor Labs now sets the default branch detection flag for all projects to true by default. Endor Labs automatically detects the new default branch and sets that as the default reference for all the projects configured with the Endor Labs SCM Apps.

For more information, see Default branch detection.

Endor Labs now enables the malware finding policy by default for all tenants. You automatically receive findings for suspicious and malicious code across all projects, helping you detect and remediate security issues faster.

For more information, see OSS finding policy.

We are excited to introduce the latest features and enhancements in Endor Labs.

CI/CD tool scanning has been discontinued and is no longer available. This change does not affect the scanning of GitHub Action dependencies.

Endor Labs now includes Endor AI Chat, an AI-powered assistant designed to help you understand vulnerabilities and take quicker, more informed action. You can ask natural language questions about security findings, scan results, package versions, and vulnerabilities. See Endor AI chat.

Endor Labs now supports pre-computed reachability analysis to determine vulnerability exposure in dependencies without requiring code compilation or full call graph generation. You can enable it using the pre-computed flag for quick scans and full scans.

For more information, see Pre-computed reachability analysis.

You can now search for authorization policies using rule criteria, creator email addresses, and namespace assignments.

For more information, see Search authorization policies.

You can now filter notifications by project name to focus on notifications from specific projects and reduce noise from others.

For more information, see Notifications.

Endor Labs now supports scanning Scala projects built with Gradle by resolving dependencies from build.gradle or build.gradle.kts files.

For more information, see Scan Scala projects.

We are excited to introduce the latest features and enhancements in Endor Labs.

CI/CD tool scanning functionality is being deprecated and will be discontinued by the end of September 2025. This change does not affect the scanning of GitHub Action dependencies.

You can now use the dedicated command endorctl container scan for container scanning. This replaces the older endorctl scan --container command. Migrate to endorctl container scan to ensure continued compatibility. For more information, see Use new container scan commands.

Deprecation notice
The old endorctl scan --container commands and their corresponding flags (--container, --container-tar, and --container-as-ref) will be removed after a three-month deprecation period.

Endor Labs now uses Opengrep to scan your code for SAST and AI model findings instead of Semgrep. Opengrep is an open-source, static analysis tool that finds bugs and vulnerabilities in the source code using pattern matching. Endor Labs automatically downloads Opengrep for you when you run a scan that needs it.

Endor Labs now supports Scan Workflow, which lets you define scan profiles as sequential steps within a single project scan. This gives you fine grained control over how scans run, allowing you to target different parts of your codebase more precisely.

You can configure a scan workflow and assign it to your project either using the Endor Labs API or through the Endor Labs user interface.

For more information see Configure Scan Workflow in Endor Labs.

Endor Labs now supports Upgrade Impact Analysis (UIA) for JavaScript and TypeScript projects. UIA helps you understand the potential impact of upgrading dependencies by identifying breaking changes and dependency conflicts that may occur during upgrades.

For more information, see Upgrade impact analysis and JavaScript/TypeScript scanning.

Endor Labs now offers policies that reduce supply chain risks by detecting newly released open source dependencies within a configurable cooldown period and optionally blocking their adoption to prevent issues from unverified packages and malware.

  • Recently Released Dependencies finding policy: Enable this finding policy to identify and raises findings for dependency versions that have been published within the defined cooldown period. Default cooldown period is 48 hours.

  • Recently Released Dependencies (Cooldown) action policy: Create an action policy from the template to define how to handle these findings.

For more information, see OSS finding policy, and Recently released dependencies action policy.

With the use of Opengrep instead of Semgrep for SAST scan, you can now run SAST scans on Windows. For more information, see SAST scan with Endor Labs.

Endor Labs now supports scanning Swift projects that use the Swift Package Manager (SwiftPM) by resolving dependencies from the Package.swift file.

For more information, see Scan Swift projects.

Endor Labs now supports filtering findings exported to GitHub Advanced Security through action policies. Findings are exported only from projects covered by configured action policies.

For more information, see Export findings to GitHub Advanced Security.

The First Party Code dashboard now features a stacked bar chart that displays the top 10 secret rules along with their corresponding findings. This enables you to identify high impact rules and prioritize remediation by severity.

For more information, see First-party code.

Endor Labs now includes vulnerability aliases in SARIF output for SCA findings. Aliases such as CVE IDs, GHSA IDs, and other OSV identifiers help you track multiple identifiers for the same vulnerability and improve integration with security tools and workflows.

You can now use the search bar to filter projects by name to focus the OSS overview on specific projects. This helps organizations prioritize the most critical and exploitable vulnerabilities, enabling more targeted security efforts.

For more information, see First-party code.

Endor Labs now supports Gradle package manager integration. You can configure private package manager repositories for Gradle through the user interface to scan dependencies from custom repositories and enhance dependency resolution.

For more information, see Gradle private package manager.

You can now filter findings by project name, allowing you to target the findings of a specific project, focus on them, and eliminate noise from other projects.

For more information, see Search for findings using basic filters.

You can now clone scan profiles in your namespace. The cloned profile retains all parameters and custom settings, helping you set up new profiles faster and maintain consistent configurations across scans.

For more information, see Clone scan profile.

We are excited to introduce the latest features and enhancements in Endor Labs.

CI/CD tool scanning functionality is being deprecated and will be discontinued by September 15, 2025. This change does not affect the scanning of GitHub Action dependencies.

AI security review provides automated code review capabilities using artificial intelligence to identify potential security issues in your code base. You can set up AI security review to review pull requests and raise findings for security issues.

For more information, see AI security review.

The first-party code dashboard provides a comprehensive view of the vulnerabilities in your codebase from a SAST and secrets perspective.

For more information, see First-party code dashboard.

You can now enable the End of Life Container Dependencies finding policy to raise findings for OS-level packages and components in container images that have reached end of life.

For more information, see Container finding policies.

Endor Labs now offers improved malware detection with detailed malware reasoning, broader coverage, and timely warnings before malicious packages disappear from registries. You can use the following new malware focused policies:

  • Malware finding policy: Enable OSS finding policy to identify known malicious code or suspicious patterns in dependencies and raise findings for them.
  • Malware action policy: Create an action policy from the malware template to define how to handle malware findings.
  • Malware exception policy: Create an exception policy to apply exceptions to malware findings under defined conditions and exclude them from action policies.

For more information, see OSS finding policy, Malware action policy, and Malware exception policy.

You can now export Software Bill of Materials in the industry standard SPDX format, with support for both json and tag-value output formats, making it easier to integrate SBOMs into existing compliance, auditing, and security workflows.

For more information see Export SBOM in Endor Labs.

The GHAS SARIF exporter now supports pull request scans for GitHub App (Pro). If you have enabled pull request scans in your GitHub App, the GHAS SARIF exporter exports the findings for each pull request. You can view the findings for the pull request in GitHub Advanced Security.

For more information, see Export findings to GitHub Advanced Security.

Endor Labs extends AI model detection to include Azure OpenAI, surfacing detected models as dependencies during scans. Azure OpenAI models are detected but not scored, as provider metadata is limited.

For more information, see AI model detection.

You can now scan container images saved as tarball files using endorctl. This helps you analyze dependencies, generate SBOM details, and review security findings for container images that are not directly accessible from a registry.

For more information, see Scan container image tarball.

You can now use the MAL identifier to search for known malware in the Endor Labs vulnerability database and quickly identify malicious packages alongside existing vulnerabilities.

For more information, see Endor Labs vulnerability database.