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 #4135

Closed
google-allstar-prod bot opened this issue Nov 7, 2023 · 73 comments · Fixed by #4205
Closed

Security Policy violation Binary Artifacts #4135

google-allstar-prod bot opened this issue Nov 7, 2023 · 73 comments · Fixed by #4205

Comments

@google-allstar-prod
Copy link

google-allstar-prod bot commented Nov 7, 2023

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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.


⚠️ There is an updated version of this policy result! Click here to see the latest update


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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

1 similar comment
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

The policy result has been updated.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

5 similar comments
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Policy is now in compliance. Closing issue.

Copy link
Author

Reopening issue. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

@google-allstar-prod google-allstar-prod bot reopened this Dec 8, 2023
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

13 similar comments
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.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.

@google-allstar-prod google-allstar-prod bot reopened this Mar 5, 2024
Copy link
Author

Reopening issue. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

4 similar comments
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-cli/src/integration-test/resources/jarTest/standard/dependency1.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/directory/dependency2.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/jarWithCp.jar
  • jib-cli/src/integration-test/resources/jarTest/standard/noDependencyJar.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

The policy result has been updated.


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

  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

3 similar comments
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/default-target/libs/dependency-1.0.0.jar
  • jib-gradle-plugin/src/integration-test/resources/gradle/projects/simple/libs/dependency-1.0.0.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.

Copy link
Author

The policy result has been updated.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

@google-allstar-prod google-allstar-prod bot reopened this May 29, 2024
Copy link
Author

Policy is now in compliance. Closing issue.

Copy link
Author

Reopening issue. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

7 similar comments
Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Updating issue after ping interval. See its status below.


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

  • examples/helloworld/gradle/wrapper/gradle-wrapper.jar
  • examples/java-agent/gradle/wrapper/gradle-wrapper.jar
  • examples/ktor/gradle/wrapper/gradle-wrapper.jar
  • examples/micronaut/gradle/wrapper/gradle-wrapper.jar
  • examples/multi-module/gradle/wrapper/gradle-wrapper.jar
  • examples/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • examples/vertx/gradle/wrapper/gradle-wrapper.jar
  • gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/jarTest/spring-boot/gradle/wrapper/gradle-wrapper.jar
  • jib-cli/src/integration-test/resources/warTest/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.

Copy link
Author

Policy is now in compliance. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants