How virustotal/.allstar works
Project type and purpose
• This repository is not a conventional application or library but a policy-as-code configuration repository for Google’s Allstar tool.
• Its sole purpose is to supply YAML policy files to govern security checks (e.g., branch protection, workflow safety, binary artifacts) in a GitHub organization.
File structure
• Top-level files:
• README.md – describes the repo’s role as a “default Allstar configuration” pointing at an upstream config.
• allstar.yaml – primary manifest that indicates “use google/allstar-config as the source of truth.”
• binary_artifacts.yaml, branch_protection.yaml, dangerous_workflow.yaml, outside.yaml, security.yaml – individual policy modules for different security domains.
• There are no code folders or build scripts. All files are atomic policy definitions consumed by Allstar.
README for additional insights
• The README confirms that this repo’s config layers on top of the upstream google/allstar-config repo.
• There are no local overrides other than enabling or disabling individual policies via the YAML modules.