> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/sbom360/projects/code-quality.md).

# Code Quality

### What is Code Quality?

Code quality is calculated by running a set of checks on the source code of each component.

This includes direct and transitive dependencies.

List of Code Quality Checks

* Binary Artifacts: Has the project generated executable (binary) artifacts in the source repository?
* CII Best Practices: Does the project have a CII Best Practices badge?
* Fuzzing: Does the project use fuzzing in OSS-Fuzz?
* Pinned Dependencies: Has the project declared and pinned its dependencies?
* CI Tests: Does the project run tests before pull requests are merged?
* Code Review: Does the project require a code review before pull/merge requests are assimilated?
* Maintained: Is the project actively maintained?

### Understanding Code Quality

<figure><img src="/files/PDcUZQYtlcE4Uo5i3qLx" alt=""><figcaption></figcaption></figure>

* Count of components that have code quality issues is displayed towards left, along with the category of the components (open-source, private, third-party, unknown).
* The code quality issue count is displayed towards the right, grouped by severity (critical, high, medium, low).
* Each tile is clickable which will list down the components applicable to that filter in a table view. The details will list the component name, version and a capsule for code quality checks.
* By clicking the code quality checks capsule, next level details will be shown as below.
* By clicking on any row, the sidesheet shows up as shown below.

<figure><img src="/files/BT7Q4Ihn3UcIyhniyRFB" alt=""><figcaption></figcaption></figure>

<br>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.veedna.com/sbom360/projects/code-quality.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.