Security Policy violation Binary Artifacts #17036

google-allstar-prod · 2022-12-15T14:18:18Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.jar
Run a Scorecards scan to see full list. (Update: a full list is available at https://gist.github.com/meteorcloudy/4935e3a7c2ba2404a5e510878c078fca)

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.

google-allstar-prod · 2022-12-16T15:25:15Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-18T03:20:29Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-20T00:27:22Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-21T08:56:17Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-23T03:39:08Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-24T08:00:01Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-25T16:39:43Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-28T11:44:22Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-30T06:22:46Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2022-12-31T16:36:00Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-01T21:15:50Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-02T23:52:55Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-04T19:40:27Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-06T02:32:08Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-07T10:51:18Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-08T12:57:01Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-09T22:16:02Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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.

meteorcloudy · 2023-01-10T13:33:16Z

#17112 provides a way to remove all jar files under third_party directory.

meteorcloudy · 2023-01-10T13:40:56Z

To disable the notification, follow bazel-contrib/rules_jvm_external@4dc6737 as an example to create an allowlist.

google-allstar-prod · 2023-01-12T03:45:46Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-13T13:40:20Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-14T15:41:33Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-15T20:05:54Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-17T05:21:58Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-19T00:10:22Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-21T12:06:32Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-22T14:14:14Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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 · 2023-01-24T00:42:21Z

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

src/main/cpp/resources.o
src/tools/singlejar/data/multi_release.jar
third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar
third_party/android_common/com.android.tools.build_builder-model_2.0.0.jar
third_party/android_common/com.android.tools.build_builder-test-api_2.0.0.jar
third_party/android_common/com.android.tools.build_builder_2.0.0.jar
third_party/android_common/com.android.tools.build_manifest-merger_25.0.0-patched.jar
third_party/android_common/com.android.tools.external.lombok_lombok-ast_0.2.3.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2-stripped.jar
third_party/android_common/com.android.tools.layoutlib_layoutlib_26.1.2.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.

@fweikert

…nal (non-third_party) Deleting more checked in jars from third_party directory, instead we fetch them using rules_jvm_external. The number of checked in jar files under third_party was reduced to 94 from 175. After this PR, we no longer need any checked-in jar files the third_party directory to bootstrap Bazel (see the update in scripts/bootstrap/compile.sh). The rest of the checked-in jar files are only for Java tools, Android tools and Java tests, which should also be migrated later. A few changes and impacts worth noting about this PR: - We no longer duplicate the list of maven coordinates in the MODULE.bazel file, it just uses the same maven_install.json file generated by rules_jvm_external from WORKSPACE. - We had to exclude some problematic jars (check the `excluded_artifacts` in WORKSPACE). - Since we don't yet have a way to handle licenses with rules_jvm_external, this PR preserves all LICENSE files and added back some LICENSE files deleted in 205ba06. License files are merged by https://github.com/bazelbuild/bazel/blob/ab71a1002c9c53a8061336e40f91204a2a32c38e/src/main/java/com/google/devtools/build/lib/runtime/commands/license/BUILD#L15 - Since rules_jvm_external respects the declared dependencies in the jar's pom.xml file. It fetches more jars than we previously checked in. Through the `jvm_import` rule, Bazel transitively depends on more jars and it causes the size of the Bazel binary to increase (about 2%, see the change in minimal_jdk_test.sh). But the overall improvement on handling maven dependencies should be worth it. - After syncing with @fweikert , the security build for Bazel we are working on should still work with this change. Overall, it should make it easier to review Bazel's maven dependencies. Working towards: #17036 Closes #17221. PiperOrigin-RevId: 511179726 Change-Id: Ic7e99d0ef5074b45aa00d3229f6d4d8855ee2311

…hird_party) This PR basically reverts #11629 and fetch android databinding jars and their dependencies with rules_jvm_external instead. We still need to keep `third_party/java/android_databinding/v3_4_0/exec.jar` because it is custom prebuilt tool and there is no corresponding maven coordinate. Working towards: #17036 Closes #17727. PiperOrigin-RevId: 516246992 Change-Id: I122ab5e9037668ac6913ab03df186609bbc0f458

It's not used anywhere except source reference. Working towards: bazelbuild#17036

It's not used anywhere except source reference. Working towards: #17036 Closes #17811. PiperOrigin-RevId: 517410193 Change-Id: Iad3ac2801d84b04b4bbeca396c4d0b6bc3199f54

It's not used anywhere except source reference. Working towards: #17036 Partial commit for third_party/*, see #17811. Signed-off-by: Yun Peng <pcloudy@google.com>

Remove checked-in jars used for `//src/test/java/...` and fetch them with rules_jvm_external instead. Working towards: #17036 Closes #17812. PiperOrigin-RevId: 518608132 Change-Id: I6a0d282febc27c538b5297054facc70a5a0ca35d

@fweikert

…nal (non-third_party) Deleting more checked in jars from third_party directory, instead we fetch them using rules_jvm_external. The number of checked in jar files under third_party was reduced to 94 from 175. After this PR, we no longer need any checked-in jar files the third_party directory to bootstrap Bazel (see the update in scripts/bootstrap/compile.sh). The rest of the checked-in jar files are only for Java tools, Android tools and Java tests, which should also be migrated later. A few changes and impacts worth noting about this PR: - We no longer duplicate the list of maven coordinates in the MODULE.bazel file, it just uses the same maven_install.json file generated by rules_jvm_external from WORKSPACE. - We had to exclude some problematic jars (check the `excluded_artifacts` in WORKSPACE). - Since we don't yet have a way to handle licenses with rules_jvm_external, this PR preserves all LICENSE files and added back some LICENSE files deleted in 205ba06. License files are merged by https://github.com/bazelbuild/bazel/blob/ab71a1002c9c53a8061336e40f91204a2a32c38e/src/main/java/com/google/devtools/build/lib/runtime/commands/license/BUILD#L15 - Since rules_jvm_external respects the declared dependencies in the jar's pom.xml file. It fetches more jars than we previously checked in. Through the `jvm_import` rule, Bazel transitively depends on more jars and it causes the size of the Bazel binary to increase (about 2%, see the change in minimal_jdk_test.sh). But the overall improvement on handling maven dependencies should be worth it. - After syncing with @fweikert , the security build for Bazel we are working on should still work with this change. Overall, it should make it easier to review Bazel's maven dependencies. Working towards: #17036 Closes #17221. PiperOrigin-RevId: 511179726 Change-Id: Ic7e99d0ef5074b45aa00d3229f6d4d8855ee2311 # Conflicts: # WORKSPACE # src/test/shell/integration/minimal_jdk_test.sh

…hird_party) This PR basically reverts bazelbuild#11629 and fetch android databinding jars and their dependencies with rules_jvm_external instead. We still need to keep `third_party/java/android_databinding/v3_4_0/exec.jar` because it is custom prebuilt tool and there is no corresponding maven coordinate. Working towards: bazelbuild#17036 Closes bazelbuild#17727. PiperOrigin-RevId: 516246992 Change-Id: I122ab5e9037668ac6913ab03df186609bbc0f458

It's not used anywhere except source reference. Working towards: bazelbuild#17036 Closes bazelbuild#17811. PiperOrigin-RevId: 517410193 Change-Id: Iad3ac2801d84b04b4bbeca396c4d0b6bc3199f54

It's not used anywhere except source reference. Working towards: bazelbuild#17036 Partial commit for third_party/*, see bazelbuild#17811. Signed-off-by: Yun Peng <pcloudy@google.com>

Remove checked-in jars used for `//src/test/java/...` and fetch them with rules_jvm_external instead. Working towards: bazelbuild#17036 Closes bazelbuild#17812. PiperOrigin-RevId: 518608132 Change-Id: I6a0d282febc27c538b5297054facc70a5a0ca35d

google-allstar-prod bot added the allstar label Dec 15, 2022

restingbull mentioned this issue Dec 16, 2022

Security Policy violation Binary Artifacts bazelbuild/rules_kotlin#884

Closed

meteorcloudy self-assigned this Jan 10, 2023

meteorcloudy added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Jan 10, 2023

meteorcloudy mentioned this issue Jan 12, 2023

Use rules_jvm_external to fetch jars dependencies #17112

Closed

meteorcloudy mentioned this issue Jan 16, 2023

Migrate more jar files under third_party directory to rules_jvm_external #17221

Closed

This was referenced Jan 19, 2023

Delete android_common v25 and references. #17249

Closed

Update turbine #17207

Closed

meteorcloudy mentioned this issue Feb 27, 2023

Remove android_common jars from third_party #17582

Closed

meteorcloudy mentioned this issue Mar 10, 2023

Fetch android_databinding dependencies with rules_jvm_external #17727

Closed

meteorcloudy added a commit to meteorcloudy/bazel that referenced this issue Mar 17, 2023

Delete checker framework from third party

0ed6acb

It's not used anywhere except source reference. Working towards: bazelbuild#17036

meteorcloudy mentioned this issue Mar 17, 2023

Delete checker framework from third party #17811

Closed

copybara-service bot pushed a commit that referenced this issue Mar 17, 2023

Delete checker framework from third party

c890ed3

It's not used anywhere except source reference. Working towards: #17036 Partial commit for third_party/*, see #17811. Signed-off-by: Yun Peng <pcloudy@google.com>

meteorcloudy mentioned this issue Mar 22, 2023

Mirgate jar dependencies for testing to rules_jvm_external #17812

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Security Policy violation Binary Artifacts #17036

Security Policy violation Binary Artifacts #17036

google-allstar-prod bot commented Dec 15, 2022 •

edited by meteorcloudy

Loading

google-allstar-prod bot commented Dec 16, 2022

google-allstar-prod bot commented Dec 18, 2022

google-allstar-prod bot commented Dec 20, 2022

google-allstar-prod bot commented Dec 21, 2022

google-allstar-prod bot commented Dec 23, 2022

google-allstar-prod bot commented Dec 24, 2022

google-allstar-prod bot commented Dec 25, 2022

google-allstar-prod bot commented Dec 28, 2022

google-allstar-prod bot commented Dec 30, 2022

google-allstar-prod bot commented Dec 31, 2022

google-allstar-prod bot commented Jan 1, 2023

google-allstar-prod bot commented Jan 2, 2023

google-allstar-prod bot commented Jan 4, 2023

google-allstar-prod bot commented Jan 6, 2023

google-allstar-prod bot commented Jan 7, 2023

google-allstar-prod bot commented Jan 8, 2023

google-allstar-prod bot commented Jan 9, 2023

meteorcloudy commented Jan 10, 2023

meteorcloudy commented Jan 10, 2023

google-allstar-prod bot commented Jan 12, 2023

google-allstar-prod bot commented Jan 13, 2023

google-allstar-prod bot commented Jan 14, 2023

google-allstar-prod bot commented Jan 15, 2023

google-allstar-prod bot commented Jan 17, 2023

google-allstar-prod bot commented Jan 19, 2023

google-allstar-prod bot commented Jan 21, 2023

google-allstar-prod bot commented Jan 22, 2023

google-allstar-prod bot commented Jan 24, 2023

Security Policy violation Binary Artifacts #17036

Security Policy violation Binary Artifacts #17036

Comments

google-allstar-prod bot commented Dec 15, 2022 • edited by meteorcloudy Loading

google-allstar-prod bot commented Dec 16, 2022

google-allstar-prod bot commented Dec 18, 2022

google-allstar-prod bot commented Dec 20, 2022

google-allstar-prod bot commented Dec 21, 2022

google-allstar-prod bot commented Dec 23, 2022

google-allstar-prod bot commented Dec 24, 2022

google-allstar-prod bot commented Dec 25, 2022

google-allstar-prod bot commented Dec 28, 2022

google-allstar-prod bot commented Dec 30, 2022

google-allstar-prod bot commented Dec 31, 2022

google-allstar-prod bot commented Jan 1, 2023

google-allstar-prod bot commented Jan 2, 2023

google-allstar-prod bot commented Jan 4, 2023

google-allstar-prod bot commented Jan 6, 2023

google-allstar-prod bot commented Jan 7, 2023

google-allstar-prod bot commented Jan 8, 2023

google-allstar-prod bot commented Jan 9, 2023

meteorcloudy commented Jan 10, 2023

meteorcloudy commented Jan 10, 2023

google-allstar-prod bot commented Jan 12, 2023

google-allstar-prod bot commented Jan 13, 2023

google-allstar-prod bot commented Jan 14, 2023

google-allstar-prod bot commented Jan 15, 2023

google-allstar-prod bot commented Jan 17, 2023

google-allstar-prod bot commented Jan 19, 2023

google-allstar-prod bot commented Jan 21, 2023

google-allstar-prod bot commented Jan 22, 2023

google-allstar-prod bot commented Jan 24, 2023

google-allstar-prod bot commented Dec 15, 2022 •

edited by meteorcloudy

Loading