codeql-coding-standards
composer-installer
codeql-coding-standards | composer-installer | |
---|---|---|
3 | 1 | |
107 | 538 | |
3.7% | -0.4% | |
9.8 | 5.7 | |
3 days ago | 6 days ago | |
CodeQL | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
codeql-coding-standards
- Misra C++:2023 Published
-
Porsche Open Source Platform
This comment chain appears to have a fundamental misconception of what constitutes safe and what does not.
Automotive standards and automotive coding standards approach safety in a different way than most people think (and given your comments I would say this includes you). If you're curious, you can have a look at some rules to evaluate automotive code that are published here: https://github.com/github/codeql-coding-standards
In short, the rules do not aim to eliminate failure or crashes, but rather make the crash predictable and uniform when a crash occurs so that it can be dealt with. This is further complicated by where and how the automotive manufacture chooses to implement safety controls. It is entirely possible to have a bunch of unsafe code running somewhere on a car, and simply have a small safety shim around said code that prevents the unsafe code from impacting the safe operation of the vehicle.
With that in mind, let's take the example that you use here of emissions cheating software. Emissions is likely not considered safety relevant (it might not even be QM, it just might be some code) and so no safety requirement applies to it. So, no real scrutiny would happen there regardless, at least from a safety perspective. See, validating that software passes a particular safety certification is time and money intensive and manufacturers therefore keep the amount of code that they qualify as safe to a minimum. This means as an example that the infotainment systems of many manufacturers are not safety relevant and no safety function should exist on or interact with them.
A few other things to consider from other threads:
- Telsa doesn't necessarily follow or adhere to safety standards. They (Telsa) are explicitly non-compliant in some cases, and this is partially why there are investigations into their practices.
- Industrial robotics code is just as bad if not worse than most automotive software from what I've seen. As you note, its that these robots are not under manual control
- None of this prevents the software from being open source. There are plenty of safety qualified open source projects. This simply limits who can contribute and how contributions are managed. The main reason why many things in automotive are not open source is that the ECU manufacturer isn't interested in doing so, and the Tier 1/2/3 that does the implementation is even less so.
- CodeQL support for Autosar and Cert C++
composer-installer
-
"phpcs" current folder directive "." does not seem to be working. Do I need a project?
I would like to recommend adding the dealerdirect/phpcodesniffer-composer-installer package as well. You don't need the post-install-cmd and post-update-cmd scripts to add the PHP-compatibility ruleset.
What are some alternatives?
codeql - CodeQL: the libraries and queries that power security researchers around the world, as well as code scanning in GitHub Advanced Security
composer-normalize - 🎵 Provides a composer plugin for normalizing composer.json.
codeql-action - Actions for running CodeQL analysis
GrumPHP - A PHP code-quality tool
codeql - CodeQL workshops for GitHub Universe
CodingStandards - A pre-defined set of coding standards for PHP CS Fixer.
cscs - A curated list of Coding Style Conventions and Standards.
PHP Code Sniffer - PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.