docs: fix url

Author: bordumb

Cargo.toml

@@ -20,7 +20,7 @@ edition = "2024"
 rust-version = "1.85.0"
 readme = "README.md"
 license = "Apache-2.0"
-repository = "https://github.com/bordumb/capsec"
+repository = "https://github.com/auths-dev/capsec"
 
 [workspace.dependencies]
 # Core

README.md

@@ -1,6 +1,6 @@
 # capsec
 
-[![CI](https://github.com/bordumb/capsec/actions/workflows/ci.yml/badge.svg)](https://github.com/bordumb/capsec/actions/workflows/ci.yml)
+[![CI](https://github.com/auths-dev/capsec/actions/workflows/ci.yml/badge.svg)](https://github.com/auths-dev/capsec/actions/workflows/ci.yml)
 [![crates.io](https://img.shields.io/crates/v/capsec.svg)](https://crates.io/crates/capsec)
 [![docs.rs](https://docs.rs/capsec/badge.svg)](https://docs.rs/capsec)
 
@@ -81,8 +81,8 @@ jobs:
 New high-risk I/O in a PR? CI fails. No new I/O? CI passes. Teams can adopt incrementally with `--baseline` and `--diff` to only flag *new* findings.
 
 To see it in action, you can reference these:
-* [CI/CD](https://github.com/bordumb/capsec/blob/main/.github/workflows/ci.yml#L57)
-* [Pre-Commit Hook](https://github.com/bordumb/capsec/blob/main/.pre-commit-config.yaml#L32)
+* [CI/CD](https://github.com/auths-dev/capsec/blob/main/.github/workflows/ci.yml#L57)
+* [Pre-Commit Hook](https://github.com/auths-dev/capsec/blob/main/.pre-commit-config.yaml#L32)
 
 ---
 

SECURITY.md

@@ -83,6 +83,6 @@ Known blind spots (documented in `capsec-tests/tests/audit_evasion.rs`):
 
 ## Reporting vulnerabilities
 
-If you discover a security issue in capsec, please email the maintainers directly rather than opening a public issue. Contact: [open an issue with the `security` label](https://github.com/bordumb/capsec/issues/new?labels=security).
+If you discover a security issue in capsec, please email the maintainers directly rather than opening a public issue. Contact: [open an issue with the `security` label](https://github.com/auths-dev/capsec/issues/new?labels=security).
 
 For issues that are not security-sensitive (e.g., audit tool false negatives, documentation gaps), please open a regular GitHub issue.

crates/capsec-core/README.md

@@ -2,7 +2,7 @@
 
 Zero-cost capability tokens and permission traits for compile-time capability-based security in Rust.
 
-This is the foundation crate of the [capsec](https://github.com/bordumb/capsec) ecosystem. You probably want to depend on the `capsec` facade crate instead of using this directly.
+This is the foundation crate of the [capsec](https://github.com/auths-dev/capsec) ecosystem. You probably want to depend on the `capsec` facade crate instead of using this directly.
 
 ## What's in here
 

crates/capsec-macro/README.md

@@ -1,6 +1,6 @@
 # capsec-macro
 
-Procedural macros for the [capsec](https://github.com/bordumb/capsec) capability-based security system.
+Procedural macros for the [capsec](https://github.com/auths-dev/capsec) capability-based security system.
 
 You probably want to depend on the `capsec` facade crate instead of using this directly — it re-exports these macros.
 

crates/capsec-std/README.md

@@ -2,7 +2,7 @@
 
 Capability-gated wrappers around `std::fs`, `std::net`, `std::env`, and `std::process`.
 
-This is the enforcement layer of [capsec](https://github.com/bordumb/capsec). Every function mirrors a `std` function but requires a capability token proving the caller has permission. You probably want to depend on the `capsec` facade crate instead of using this directly.
+This is the enforcement layer of [capsec](https://github.com/auths-dev/capsec). Every function mirrors a `std` function but requires a capability token proving the caller has permission. You probably want to depend on the `capsec` facade crate instead of using this directly.
 
 ## Example
 

crates/cargo-capsec/src/main.rs

@@ -419,7 +419,7 @@ fn run_badge(args: BadgeArgs) {
         // Markdown badge
         let encoded_message = message.replace(' ', "%20");
         println!(
-            "[![capsec](https://img.shields.io/badge/capsec-{encoded_message}-{color})](https://github.com/bordumb/capsec)"
+            "[![capsec](https://img.shields.io/badge/capsec-{encoded_message}-{color})](https://github.com/auths-dev/capsec)"
         );
     }
 }

crates/cargo-capsec/src/reporter.rs

@@ -389,8 +389,8 @@ pub fn report_sarif(
                     "text": format!("{}. Detected by capsec static analysis.", f.description)
                 },
                 "help": {
-                    "text": format!("{}\n\nSee https://github.com/bordumb/capsec for details on capability-based security in Rust.", f.description),
-                    "markdown": format!("**{}**\n\n[capsec documentation](https://github.com/bordumb/capsec)", f.description)
+                    "text": format!("{}\n\nSee https://github.com/auths-dev/capsec for details on capability-based security in Rust.", f.description),
+                    "markdown": format!("**{}**\n\n[capsec documentation](https://github.com/auths-dev/capsec)", f.description)
                 },
                 "defaultConfiguration": {
                     "level": risk_to_sarif_level(f.risk)
@@ -456,8 +456,8 @@ pub fn report_sarif(
                         "text": "A crate declared as 'pure' in [package.metadata.capsec] has ambient authority findings. Pure crates must not perform I/O."
                     },
                     "help": {
-                        "text": "Either remove the I/O operations or change the classification to 'resource'.\n\nSee https://github.com/bordumb/capsec for details.",
-                        "markdown": "**Purity violation**: either remove I/O or reclassify as `resource`.\n\n[capsec documentation](https://github.com/bordumb/capsec)"
+                        "text": "Either remove the I/O operations or change the classification to 'resource'.\n\nSee https://github.com/auths-dev/capsec for details.",
+                        "markdown": "**Purity violation**: either remove I/O or reclassify as `resource`.\n\n[capsec documentation](https://github.com/auths-dev/capsec)"
                     },
                     "defaultConfiguration": {
                         "level": "error"
@@ -493,7 +493,7 @@ pub fn report_sarif(
                     "name": "capsec-cli",
                     "version": env!("CARGO_PKG_VERSION"),
                     "semanticVersion": env!("CARGO_PKG_VERSION"),
-                    "informationUri": "https://github.com/bordumb/capsec",
+                    "informationUri": "https://github.com/auths-dev/capsec",
                     "rules": rules
                 }
             },

docs/blog/ecosystem-audit-report.md

@@ -1,7 +1,7 @@
 # What Can Your Dependencies Do? An Ambient Authority Audit of the Rust Ecosystem
 
 **Date:** 2026-03-19
-**Tool:** [capsec](https://github.com/bordumb/capsec) — static capability audit for Rust
+**Tool:** [capsec](https://github.com/auths-dev/capsec) — static capability audit for Rust
 
 ## Introduction
 

scripts/releases/1_github.py

@@ -161,7 +161,7 @@ def main() -> None:
         sys.exit(1)
 
     print(f"\nDone. Release workflow will run at:")
-    print(f"  https://github.com/bordumb/capsec/actions")
+    print(f"  https://github.com/auths-dev/capsec/actions")
 
 
 if __name__ == "__main__":