jspecify / jspecify/jdk

Security Policy violation Binary Artifacts

Open
#2 29 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

allstar
Dominant language
Java
Stars
7
Forks
3
Avg merge
15h 17m
Merged PRs (30d)
8

Description

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

First 10 Artifacts Found

  • checker-qual.jar
  • test/hotspot/jtreg/runtime/7116786/testcases.jar
  • test/hotspot/jtreg/runtime/ClassFile/JsrRewritingTestCase.jar
  • test/hotspot/jtreg/runtime/ClassFile/testcase.jar
  • test/hotspot/jtreg/runtime/EnclosingMethodAttr/enclMethodAttr.jar
  • test/hotspot/jtreg/runtime/LocalVariableTable/testcase.jar
  • test/hotspot/jtreg/runtime/classFileParserBug/emptynumbootstrapmethods.jar
  • test/hotspot/jtreg/runtime/classFileParserBug/test.jar
  • test/hotspot/jtreg/runtime/duplAttributes/test.jar
  • test/jdk/java/beans/Introspector/7064279/test.jar
  • Run a Scorecards scan to see full list.

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.


Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the listed JAR files, including checker-qual.jar and the artifacts under test/hotspot/jtreg and test/jdk. Run a Scorecards scan to find the complete set, remove generated executable artifacts from the repository, and rerun the scan until the Binary Artifacts policy is compliant.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.