Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Policy violation Binary Artifacts #2

Closed
allstar-app bot opened this issue Apr 22, 2022 · 2 comments · Fixed by #9
Closed

Security Policy violation Binary Artifacts #2

allstar-app bot opened this issue Apr 22, 2022 · 2 comments · Fixed by #9

Comments

@allstar-app
Copy link

allstar-app bot commented Apr 22, 2022

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.

Artifacts Found

  • bitfunk-version-catalog-accessor/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar

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.


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.

@allstar-app allstar-app bot added the allstar label Apr 22, 2022
@allstar-app
Copy link
Author

allstar-app bot commented Apr 23, 2022

Updating issue after ping interval. Status:
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.

Artifacts Found

  • bitfunk-version-catalog-accessor/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar

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.

@github-actions github-actions bot removed the allstar label Apr 24, 2022
@wmontwe wmontwe mentioned this issue Apr 26, 2022
9 tasks
@wmontwe
Copy link
Member

wmontwe commented Apr 26, 2022

Fixed by #9

@wmontwe wmontwe closed this as completed Apr 26, 2022
@wmontwe wmontwe linked a pull request Apr 26, 2022 that will close this issue
9 tasks
This was referenced May 4, 2022
@wmontwe wmontwe mentioned this issue Nov 4, 2022
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant