scorecard/docs
David A. Wheeler 8b7da7c472
📖 Improve rationale for Binary-Artifacts (#1016)
* Improve rationale for Binary-Artifacts

I'm fine with prohibiting binary executables, but
the *rationale* for doing this was completely unclear.

This commit rewrites the rationale to explain, in hopefully
a better way, why they can be a problem.

I prefer "executable" over "binary".
On digital computers, all data (including source code) are binaries :-).
In addition, some executables are simultaneously executables
and source code, e.g., shell scripts.
So I think what is meant here is a "generated binary".

I don't really think this merits a "High" level, but that's
a different dicussion.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>

* Tweak Binary-Artifacts rationale

Tweak Binary-Artifacts text based on comments from
@naveensrinivasan.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>

Co-authored-by: Naveen <172697+naveensrinivasan@users.noreply.github.com>
2021-09-14 23:48:15 +00:00
..
checks 📖 Improve rationale for Binary-Artifacts (#1016) 2021-09-14 23:48:15 +00:00
checks.md 📖 Improve rationale for Binary-Artifacts (#1016) 2021-09-14 23:48:15 +00:00