Repository navigation
Scorecard, least-privilege release report, dev lock that installs on Windows - #11
Merged
Merged
Conversation
release-security.yml gave contents: write to the whole workflow. Only the job that uploads the report needs it; the workflow now defaults to read. Scorecard's Token-Permissions scored 0 on it.
The lock lacked pywin32, which requirements-dev.in names, and win-unicode-console, so pip --require-hashes refused it on Windows. Recompiled with the command in requirements-dev.in; typing-extensions drops out, as nothing in the current pins needs it.
Scorecard publishes on every change to main and weekly, and the README shows its badge. SECURITY.md says which of its checks do not fit a VBA library built locally, and describes the YARA updater's pull requests merging themselves once the three checks pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenSSF Scorecard (published results, README badge), as in the other repositories. No fuzzing (VBA runs only in Office) and no release provenance (built locally); SECURITY.md says so.
release-security.yml's contents: write moves from the workflow to the one job that uploads, which takes Token-Permissions from 0 to 10 in a local run.
requirements-dev.txt was missing pywin32 and win-unicode-console, so it would not install on Windows; recompiled with its own command and checked to install there. test_source_contract passes with the Unreleased heading.