Builds
Read build security reports
Open an eligible Java build’s security report to compare detected packaged components with known OSV vulnerability records. Datapack builds do not have this Java report.
Open a report
Section titled “Open a report”- Open Build history.
- Find the eligible build.
- Select its Security scan control.
- Read the status, result, scope, and scan time.
- Choose View security details for the complete report.
Check the build number before interpreting a result. A report belongs to a particular build and may not describe source or dependencies changed afterward.
Understand the status
Section titled “Understand the status”| State | Meaning | Next step |
|---|---|---|
| Completed, no findings | The scan found no known vulnerabilities in the components it checked. | Continue reviewing and testing the project. |
| Completed, findings present | One or more scanned components match known vulnerability records. | Inspect affected versions and remediation options. |
| Failed or unavailable | The scan did not produce a reliable result. | Treat the result as unknown; inspect details and check a later successful scan. |
A failed scan does not stop a successful build from producing an artifact. Do not interpret scanner failure as a clean result.
Read a finding
Section titled “Read a finding”The report can include the component name/version, vulnerability identifier, summary, available severity data, affected/fixed-version information, and reference links.
Read the linked advisory for the affected component. Confirm that a proposed fixed version exists and is compatible with your project’s Minecraft target and other dependencies. Severity data may be absent; absence does not establish that a finding is harmless.
Request a remediation
Section titled “Request a remediation”- Identify the dependency and vulnerability from the report.
- Ask Buildryn to explain how the component enters the artifact and whether an update is compatible.
- Review the proposed update.
- Replace an uploaded dependency JAR if that is the relevant component, or update the generated build configuration through the reviewed change.
- Build again and inspect the report for the new build.
- Test functionality after the dependency update.
Build #<number> reports <vulnerability identifier> in <component/version>.Explain the dependency path and propose a compatible update for our target.Preserve the existing integration and identify tests needed after the update.Do not delete a required component blindly: the plugin may no longer build or start. Use dependency management for uploaded JARs.
Understand the report’s scope
Section titled “Understand the report’s scope”The report covers known vulnerabilities in detected Java dependencies. Review source code and test generated logic, permissions, data handling, and network behavior as well. Check the scan scope to see which uploaded components it covered.