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

AttributeError: 'NoneType' object has no attribute 'address' #63

Open
teknogeek opened this issue Mar 12, 2017 · 45 comments
Open

AttributeError: 'NoneType' object has no attribute 'address' #63

teknogeek opened this issue Mar 12, 2017 · 45 comments
Labels

Comments

@teknogeek
Copy link

teknogeek commented Mar 12, 2017

This issue was automatically created by Allstar and refers to trailofbits/manticore.

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

  • examples/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • tests/native/binaries/basic_linux_armv7
  • tests/native/binaries/basic_state_merging
  • 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.


⚠️ 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.

@offlinemark
Copy link
Contributor

I believe the underlying issue is due to the file being -pie. possibly also related to it being a .so

@offlinemark
Copy link
Contributor

heap0.zip

@offlinemark
Copy link
Contributor

Now I get something like this

017-06-30 13:29:38,827: [3674] PLATFORM:DEBUG: sys_brk(0x00000000) -> 0x56558000
017-06-30 13:29:39,737: [3674] PLATFORM:DEBUG: sys_newuname(...) -> Linuxubuntu4.4.0-77-generic#98 SMP Fri Jun 30 13:29:39 ART 2017i386
017-06-30 13:29:39,864: [3674] PLATFORM:DEBUG: access(/etc/ld.so.nohwcap, 0) -> False
017-06-30 13:29:40,062: [3674] PLATFORM:DEBUG: sys_mmap(0x00000000f7fff000 [requested: 0x0000000000000000], 0x1000, rw , 22, 4294967295) - (0xf7fff000)
017-06-30 13:29:41,283: [3674] PLATFORM:DEBUG: READLINK 3221050284 bfffec94 4096 -> /tmp/heap0
017-06-30 13:29:41,891: [3674] PLATFORM:DEBUG: access(/etc/ld.so.preload, 4) -> False
017-06-30 13:29:42,723: [3674] PLATFORM:INFO: Could not open file /usr/local/lib/tls/libpwnableharness32.so. Reason [Errno 2] No such file or directory: '/usr/local/lib/tls/libpwnableharness32.so'
017-06-30 13:29:42,791: [3674] PLATFORM:INFO: Could not open file /usr/local/lib/tls. Reason [Errno 2] No such file or directory: '/usr/local/lib/tls'
017-06-30 13:29:42,794: [3674] PLATFORM:DEBUG: sys_fstat64 -1
017-06-30 13:29:42,798: [3674] PLATFORM:DEBUG: sys_close(-1)
017-06-30 13:29:42,883: [3674] PLATFORM:INFO: Could not open file /usr/local/lib/libpwnableharness32.so. Reason [Errno 2] No such file or directory: '/usr/local/lib/libpwnableharness32.so'
017-06-30 13:29:42,925: [3674] PLATFORM:INFO: Could not open file /usr/local/lib. Reason [Errno 21] Is a directory: '/usr/local/lib'
017-06-30 13:29:42,926: [3674] PLATFORM:DEBUG: sys_fstat64 -1
017-06-30 13:29:42,930: [3674] PLATFORM:DEBUG: sys_close(-1)
017-06-30 13:29:43,037: [3674] PLATFORM:INFO: Could not open file /tmp/tls/libpwnableharness32.so. Reason [Errno 2] No such file or directory: '/tmp/tls/libpwnableharness32.so'
017-06-30 13:29:43,074: [3674] PLATFORM:INFO: Could not open file /tmp/tls. Reason [Errno 2] No such file or directory: '/tmp/tls'
017-06-30 13:29:43,074: [3674] PLATFORM:DEBUG: sys_fstat64 -1
017-06-30 13:29:43,078: [3674] PLATFORM:DEBUG: sys_close(-1)
017-06-30 13:29:43,149: [3674] PLATFORM:INFO: Could not open file /tmp/libpwnableharness32.so. Reason [Errno 2] No such file or directory: '/tmp/libpwnableharness32.so'
017-06-30 13:29:43,187: [3674] PLATFORM:INFO: Could not open file /tmp. Reason [Errno 21] Is a directory: '/tmp'
017-06-30 13:29:43,188: [3674] PLATFORM:DEBUG: sys_fstat64 -1
017-06-30 13:29:43,191: [3674] PLATFORM:DEBUG: sys_close(-1)
017-06-30 13:29:43,297: [3674] PLATFORM:DEBUG: Opening file /etc/ld.so.cache for r real fd 6
017-06-30 13:29:43,319: [3674] PLATFORM:DEBUG: sys_fstat64 3
017-06-30 13:29:43,342: [3674] PLATFORM:DEBUG: sys_close(3)
017-06-30 13:29:43,504: [3674] PLATFORM:INFO: Could not open file /lib32/tls/libpwnableharness32.so. Reason [Errno 2] No such file or directory: '/lib32/tls/libpwnableharness32.so'
017-06-30 13:29:43,540: [3674] PLATFORM:INFO: Could not open file /lib32/tls. Reason [Errno 2] No such file or directory: '/lib32/tls'
017-06-30 13:29:43,546: [3674] EXECUTOR:ERROR: Exception: 'NoneType' object has no attribute 'stat'
raceback (most recent call last):
 File "/mnt/hgfs/code/manticore/manticore/core/executor.py", line 463, in run
   if not current_state.execute():
 File "/mnt/hgfs/code/manticore/manticore/core/state.py", line 119, in execute
   result = self.platform.execute()
 File "/mnt/hgfs/code/manticore/manticore/platforms/linux.py", line 1810, in execute
   self.syscall()
 File "/mnt/hgfs/code/manticore/manticore/platforms/linux.py", line 1655, in syscall
   return self._syscall_abi.invoke(implementation)
 File "/mnt/hgfs/code/manticore/manticore/core/cpu/abstractcpu.py", line 312, in invoke
   result = model(*argument_tuple)
 File "/mnt/hgfs/code/manticore/manticore/platforms/linux.py", line 1955, in sys_stat64
   return self._stat(path, buf, True)
 File "/mnt/hgfs/code/manticore/manticore/platforms/linux.py", line 1963, in _stat
   ret = self.sys_fstat64(fd, buf)
 File "/mnt/hgfs/code/manticore/manticore/platforms/linux.py", line 1909, in sys_fstat64
   stat = self.files[fd].stat()
ttributeError: 'NoneType' object has no attribute 'stat'

017-06-30 13:29:43,559: [3637] MANTICORE:WARNING: Using shared context without a lock
017-06-30 13:29:43,566: [3637] MANTICORE:INFO: Results in /tmp/mcore_46nFbG
017-06-30 13:29:43,566: [3637] MANTICORE:INFO: Instructions executed: 7504
017-06-30 13:29:43,566: [3637] MANTICORE:INFO: Coverage: 3337 different instructions executed
017-06-30 13:29:43,566: [3637] MANTICORE:INFO: Total time: 5.33373093605
017-06-30 13:29:43,566: [3637] MANTICORE:INFO: IPS: 1406

@yan
Copy link
Contributor

yan commented Aug 7, 2017

fd/fstat-related issues have been fixed in past commits. This example currently terminates failing to load libpwnableharness32.so, which is unrelated to this issue. Closing.

@yan yan closed this as completed Aug 7, 2017
Copy link

allstar-app bot commented Mar 1, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • Run a Scorecards scan to see full list.

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

@allstar-app allstar-app bot reopened this Mar 1, 2024
Copy link

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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.

21 similar comments
Copy link

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 2, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 6, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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.

14 similar comments
Copy link

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 7, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 8, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 8, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 8, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 8, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 8, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 8, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 9, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 9, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 10, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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

allstar-app bot commented Mar 10, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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.

@offlinemark
Copy link
Contributor

@ekilmer Not sure what happened, but I'm getting daily emails about this. I could just unsubscribe, but it seems this adds a new comment several times per day which is not great long term. Just FYI :)

Copy link

allstar-app bot commented Mar 10, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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.

1 similar comment
Copy link

allstar-app bot commented Mar 11, 2024

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/linux/binaries/corruption
  • examples/linux/binaries/multiple-styles
  • examples/script/aarch64/basic
  • examples/script/aarch64/hello42
  • examples/wasm/collatz/collatz.wasm
  • examples/wasm/if_check/if_check.wasm
  • tests/native/binaries/arguments
  • tests/native/binaries/arguments_linux_amd64
  • tests/native/binaries/arguments_linux_armv7
  • tests/native/binaries/basic_linux_amd64
  • 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.

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

No branches or pull requests

3 participants