compliance adapted in the docs

.github/CODEOWNERS

@@ -0,0 +1,18 @@
+# Each line is a file pattern followed by one or more owners.
+# Order matters — later rules take precedence.
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+# Default owners for everything in the repo
+*                       @trimble-oss/platform-sdk-maintainers
+
+# Docs
+/docs/                  @trimble-oss/platform-sdk-maintainers
+
+# Reference Guide
+/reference-guide/       @trimble-oss/platform-sdk-maintainers
+
+# Release Notes
+/release-notes/         @trimble-oss/platform-sdk-maintainers
+
+# Samples
+/samples/               @trimble-oss/platform-sdk-maintainers

MAINTAINERS.md

@@ -0,0 +1,27 @@
+# Maintainers
+
+This document lists the maintainers of the Trimble Identity SDK for Java.
+
+## Active Maintainers
+
+<!-- Update this table with the current maintainers of the project. -->
+
+| Name | GitHub Handle | Role |
+| ---- | ------------- | ---- |
+| Vinesh Paramasivam | [vineshparamasivam](https://github.com/vineshparamasivam)  | Lead Maintainer |
+| Harshitha P | [harshitha-p-trimble](https://github.com/harshitha-p-trimble)  | Maintainer |
+| Karthik K | [karthikkandasamy21](https://github.com/karthikkandasamy21)  | Maintainer |
+
+## Responsibilities
+
+Maintainers are responsible for:
+
+- Reviewing and merging pull requests
+- Triaging issues and feature requests
+- Publishing new releases to [Maven Central](https://central.sonatype.com/search?q=trimble-id&namespace=com.trimble)
+- Keeping documentation and samples up to date
+- Enforcing the project's [security policy](./SECURITY.md)
+
+## Becoming a Maintainer
+
+If you are interested in becoming a maintainer, please reach out to [support@trimble.com](mailto:support@trimble.com).

SECURITY.md

@@ -0,0 +1,17 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+Report security vulnerabilities by emailing the Trimble Cybersecurity team at:
+
+    cybersecurity@trimble.com
+
+Report security vulnerabilities in third-party modules to the person or team maintaining the module.
+
+## Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps:
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible.