Initial sanitizer configurations

.bazelversion

@@ -0,0 +1 @@
+8.3.0

.github/ISSUE_TEMPLATE/bug_fix.md

@@ -0,0 +1,11 @@
+---
+name: Bugfix
+about: 'Issue to track a bugfix'
+title: 'Bugfix: Your bugfix title'
+labels: 'codeowner_review'
+assignees: ''
+
+---
+
+> [!IMPORTANT]
+> Make sure to link this issue with the PR for your bugfix.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,24 @@
+---
+name: Bug report
+about: Create a report for a bug
+title: 'Bug: Your bug title'
+labels: 'bug'
+assignees: ''
+
+---
+
+### Describe the bug:
+<!-- A clear and concise description of what the bug is. -->
+
+### Steps to reproduce the behavior:
+1.
+2.
+
+### Observed behavior:
+
+### Expected behavior:
+
+### Occurrence:
+<!-- Sporadic / Always -->
+
+### Attachments / Logs:

.github/ISSUE_TEMPLATE/improvement.md

@@ -0,0 +1,11 @@
+---
+name: Improvement
+about: 'Issue to track a improvement'
+title: 'Improvement: Your improvement title'
+labels: 'codeowner_review'
+assignees: ''
+
+---
+
+> [!IMPORTANT]
+> Make sure to link this issue with the PR for your improvement.

.github/PULL_REQUEST_TEMPLATE/bug_fix.md

@@ -0,0 +1,19 @@
+# Bugfix
+
+> [!IMPORTANT]
+> Use this template only for bugfixes that do not influence topics covered by contribution requests or improvements.
+
+> [!CAUTION]
+> Make sure to submit your pull-request as **Draft** until you are ready to have it reviewed by the Committers.
+
+## Description
+
+[A short description of the bug being fixed by the contribution.]
+
+## Related ticket
+
+> [!IMPORTANT]
+> Please replace `[ISSUE-NUMBER]` with the issue-number that tracks this bug fix. If there is no such
+> ticket yet, create one via [this issue template](../ISSUE_TEMPLATE/new?template=bug_fix.md).
+
+closes [ISSUE-NUMBER] (bugfix ticket)

.github/PULL_REQUEST_TEMPLATE/improvement.md

@@ -0,0 +1,19 @@
+# Improvement
+
+> [!IMPORTANT]
+> Use this template only for improvement that do not influence topics covered by contribution requests or bug fixes.
+
+> [!CAUTION]
+> Make sure to submit your pull-request as **Draft** until you are ready to have it reviewed by the Committers.
+
+## Description
+
+[A short description of the improvement being addressed by the contribution.]
+
+## Related ticket
+
+> [!IMPORTANT]
+> Please replace `[ISSUE-NUMBER]` with the issue-number that tracks this bug fix. If there is no such
+> ticket yet, create one via [this issue template](../ISSUE_TEMPLATE/new?template=improvement.md).
+
+closes [ISSUE-NUMBER] (improvement ticket)

.github/pull_request_template.md

@@ -0,0 +1,33 @@
+<!-- markdownlint-disable MD013 Line breaks on the bullet list lines are also present on the github renderer, therefore no line length limitation -->
+<!-- markdownlint-disable MD041 On the github PR template we want to start with '## Headline' -->
+
+## Notes for Reviewer
+<!-- Items in addition to the checklist below that the reviewer should look for -->
+
+## Pre-Review Checklist for the PR Author
+
+* [ ] PR title is short, expressive and meaningful
+* [ ] Commits are properly organized
+* [ ] Relevant issues are linked in the [References](#references) section
+* [ ] Tests are conducted
+* [ ] Unit tests are added
+
+## Checklist for the PR Reviewer
+
+* [ ] Commits are properly organized and messages follow [S-CORE commit guidelines](https://eclipse-score.github.io/score/main/contribute/contribution_request/index.html)
+* [ ] Unit tests have been written for new behavior
+* [ ] Public API is documented
+* [ ] PR title describes the changes
+
+## Post-review Checklist for the PR Author
+
+* [ ] All open points are addressed and tracked via issues
+
+## References
+
+<!-- Use either 'Closes #123' or 'Relates to #123' to reference the corresponding issue. -->
+
+Closes # <!-- Add issue number after '#' -->
+
+<!-- markdownlint-enable MD041 -->
+<!-- markdownlint-enable MD013 -->

.github/workflows/tests.yml

@@ -0,0 +1,57 @@
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
+
+name: Tests
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+
+jobs:
+  test-sanitizers:
+    name: Test ${{ matrix.config }}
+    runs-on: ubuntu-24.04
+
+    strategy:
+      fail-fast: false
+      matrix:
+        config:
+          - asan_ubsan_lsan
+          - tsan
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Setup Bazel
+        uses: bazel-contrib/setup-bazel@0.18.0
+        with:
+          bazelisk-cache: true
+          cache-save: ${{ github.event_name == 'push' }}
+
+      - name: Test with ${{ matrix.config }}
+        working-directory: tests
+        run: bazel test --config=${{ matrix.config }} //... --verbose_failures
+
+      - name: Upload test logs on failure
+        if: failure()
+        uses: actions/upload-artifact@v7
+        with:
+          name: testlogs-${{ matrix.config }}-${{ github.run_id }}
+          path: tests/bazel-testlogs/**/test.log
+          if-no-files-found: ignore

.gitignore

@@ -0,0 +1,15 @@
+# Bazel build outputs
+bazel-*
+.bazel-*
+
+# IDE files
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS files
+.DS_Store
+Thumbs.db
+*.lock

BUILD.bazel

@@ -0,0 +1,20 @@
+# *******************************************************************************
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+# *******************************************************************************
+
+exports_files(
+    [
+        "LICENSE.md",
+        "NOTICE",
+    ],
+    visibility = ["//visibility:public"],
+)

CONTRIBUTION.md

@@ -0,0 +1,15 @@
+# score_cpp_policies Contribution Guide
+
+The [Eclipse Safe Open Vehicle Core (S-CORE)](https://projects.eclipse.org/projects/automotive.score) project develops an open-source core stack for Software Defined Vehicles (SDVs). This repository centralizes the shared C++ quality tool policies (sanitizers, clang-tidy, clang-format) that S-CORE modules reuse to maintain consistent, safety-focused defaults.
+
+Project communication happens via the [score-dev mailing list](https://accounts.eclipse.org/mailing-list/score-dev), GitHub issues and pull requests, and Slack.
+
+Please note that the [Eclipse Foundation's Terms of Use](https://www.eclipse.org/legal/terms-of-use/) apply. Contributors must sign both the [ECA](https://www.eclipse.org/legal/ECA.php) and the [DCO](https://www.eclipse.org/legal/dco/).
+
+## Contributing changes
+
+1. Open an issue describing the policy change you propose (e.g., enabling/disabling a sanitizer option or clang-tidy rule) and the rationale, including links to any affected projects.
+2. Submit a PR referencing the issue. Keep changes minimal and well-documented, and include examples that justify the chosen defaults when possible.
+3. Request reviews from the S-CORE committers. Follow the commit message rules in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#resources-commit).
+
+If you are new to the project, see the S-CORE process descriptions and templates at [https://eclipse-score.github.io/score/process_description/](https://eclipse-score.github.io/score/process_description/).