GitHub

mamedev/mame

 2k forks
 9k stars

Description

MAME

Homepage

https://github.com/mamedev/mame

Project metadata as of .

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

View information about checks and how to fix failures.

Score
5/10
Scorecard as of .
Maintained
10/10
Determines if the project is "actively maintained".
Reasoning
30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Code-Review
4/10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning
Found 14/30 approved changesets -- score normalized to 4
CII-Best-Practices
0/10
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning
no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow
10/10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning
no dangerous workflow patterns detected
Token-Permissions
10/10
Determines if the project's workflows follow the principle of least privilege.
Reasoning
GitHub workflow tokens follow principle of least privilege
Security-Policy
0/10
Determines if the project has published a security policy.
Reasoning
security policy file not detected
License
9/10
Determines if the project has defined a license.
Reasoning
license file detected
Signed-Releases
0/10
Determines if the project cryptographically signs release artifacts.
Reasoning
Project has not signed or included provenance with any releases.
Branch-Protection
3/10
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning
branch protection is not maximal on development and all release branches
SAST
0/10
Determines if the project uses static code analysis.
Reasoning
SAST tool is not run on all commits -- score normalized to 0
Binary-Artifacts
0/10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning
binaries present in source code
Fuzzing
10/10
Determines if the project uses fuzzing.
Reasoning
project is fuzzed
Pinned-Dependencies
3/10
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning
dependency not pinned by hash detected -- score normalized to 3
Vulnerabilities
6/10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning
4 existing vulnerabilities detected