You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
P1 — supply chain & disclosure infrastructure:
- deny.toml: license/advisory/bans/sources policy for cargo-deny
- .github/dependabot.yml: weekly auto-PRs for both GitHub Actions and
Cargo deps; minor+patch updates grouped to reduce PR noise
- SECURITY.md: private-disclosure policy, scope, supported versions
P2 — passive hardening:
- .github/CODEOWNERS: require @NeuralEmpowerment review on .github/**,
Cargo.{toml,lock}, SECURITY.md, LICENSE (supply-chain + legal gates)
- .gitignore: append patterns for certs, keys, keystores, .env files
DONE_WITH_CONCERNS — cargo-deny license violations (fastembed transitives):
1. libfuzzer-sys v0.4.12 — license "(MIT OR Apache-2.0) AND NCSA"
NCSA (University of Illinois/NCSA Open Source License) is OSI-approved
and FSF-Free but is not in the current allow list.
Chain: fastembed → image → ravif → rav1e → libfuzzer-sys
2. webpki-roots v0.26.11 and v1.0.7 — license "CDLA-Permissive-2.0"
Community Data License Agreement (permissive variant) — not in allow list.
Chain: fastembed → ureq (and ort-sys) → webpki-roots
ACTION REQUIRED: Review whether NCSA and CDLA-Permissive-2.0 are
acceptable for your use case, then either add them to deny.toml
[licenses].allow or open an issue with the fastembed maintainers.
Do NOT blindly allow without legal review.
If you discover a security vulnerability in semrouter, please report it privately. **Do not open a public issue.**
6
+
7
+
**Preferred channel:**[GitHub Security Advisories](https://github.com/AgentParadise/semrouter/security/advisories/new) — this creates a private discussion with the maintainers.
8
+
9
+
**Alternative:** Open a private issue or DM a maintainer on GitHub.
10
+
11
+
We will:
12
+
- Acknowledge receipt within 7 days.
13
+
- Investigate and confirm or deny the issue within 30 days.
14
+
- Coordinate disclosure timing once a fix is ready.
15
+
- Credit the reporter in the security advisory unless they prefer to remain anonymous.
16
+
17
+
## Scope
18
+
19
+
Vulnerabilities we consider in scope:
20
+
21
+
- Memory safety issues in unsafe code (we have ~zero unsafe; any is in scope)
- Denial-of-service via inputs that cause unbounded resource consumption
24
+
- Supply-chain issues (e.g. a transitive dependency CVE we should pin away from)
25
+
26
+
Out of scope:
27
+
- The accuracy or quality of routing decisions (that's an evaluation question, not security).
28
+
- Issues in third-party embedders the consumer brings via the `EmbeddingProvider` trait.
29
+
- Reports that boil down to "your dep tree includes crate X which has known issue Y" — please file these against the upstream crate; we follow security advisories via cargo-audit and Dependabot.
30
+
31
+
## Versions
32
+
33
+
We provide security updates for:
34
+
35
+
- The latest published `0.x` version on crates.io.
36
+
- The `main` branch of the GitHub repo.
37
+
38
+
Older versions are not supported. If you need a fix for a specific version, open an issue.
0 commit comments