These credentials are stored only in your browser's localStorage and sent to the local proxy server.
They are never sent to any third party.
Interlynk token is read automatically from ~/.lynk-mcp/token.env by the proxy.
🔒 Credentials are managed centrally by IT.
This deployment reads its Interlynk, Bitbucket, Codacy and Teams credentials server-side
(AWS Secrets Manager). Nothing is entered or stored in your browser — your access is
governed entirely by your Microsoft sign-in.
Your Bitbucket account email address — used together with the API token for authentication.
Generate at: Bitbucket → your profile → Personal Settings → API tokens → Create API token → tick Repositories: Read and Projects: Read → Copy token.
Change to your API Gateway URL when deploying to AWS
In Teams: open a channel → ··· → Workflows → search "webhook" → select "Send webhook alerts to a channel" → Next → copy the generated URL. (The old Incoming Webhook connector was retired by Microsoft in 2025.)
Rules run after each dashboard refresh. A 4-hour cooldown prevents duplicate alerts.
Generate at: Codacy → Your Profile → Access Tokens → Add personal API token. Token is stored only in your browser's localStorage and never sent to third parties.
The slug shown in your Codacy URL: app.codacy.com/organizations/bb/YOUR-SLUG/repositories. Click 🔍 Look up to auto-detect it from your token.
AiDashSecurity Posture
—
Total Products ⓘ
—
loading…
▸ INTERLYNK
KEV Count ⓘ
—
actively exploited
Critical CVEs ⓘ
—
org-wide
High CVEs ⓘ
—
org-wide
Active Repos ⓘ
—
with SBOM
Config Health ⓘ
—
fully configured
SAST Issues ⓘ
—
error + warning
▸ CODACY
In Codacy ⓘ
—
repos connected
▸ CODACY
⚠ Fix These First ⓘFull dataset · ranked by blast radius × KEV × CVSS
Loading…
💥 Blast Radius ⓘCVEs affecting multiple repos · click to drill in
Analysing…
🔧 Risky to Fix ⓘCritical CVEs + low test coverage
Loading…
🏷 By Team ⓘrepo-level table · ⬇ CSV per team
Loading…
📡 Scan Events ⓘ
Loading…
Teamⓘ
Loading products…
💡How to use this tab:
Inspect a repo from the Products tab — its per-repo breakdown, fix availability, and SBOM quality will load here automatically.
For org-wide prioritisation, see the Overview tab (requires Fetch All).
License Risk is always populated org-wide.
🛠 Fix Availability ⓘloaded per product on drilldown
👆
No product selected yet
Go to the Inventory tab, find a repo with an SBOM, and click 🔧 Fix Guide → to load its breakdown here.
⚖ License Risk ⓘloading…
Loading…
🩺 SBOM Quality ⓘloaded per product on drilldown
🩺
No product selected yet
SBOM quality findings load automatically when you inspect a product. Low-quality SBOMs mean your CVE count may be understated.
Team
Loading…
Loading…
Fetching…
Blast Radius
All repos affected by this CVE · click ⬇ to export
Step 1 — Fetch Complete Data
Reports need data from every product, not a 100-CVE sample. Click Fetch All to iterate through all products with SBOMs, pull the latest version's CVEs (up to 200 per product), and build a complete dataset.
Takes ~30–60 seconds for 100+ products. Uses the existing proxy — no extra setup needed.
Starting…0%
No full data loaded yet
Step 2 — Download Reports
🔧 Team Remediation
Every CVE per product, grouped by team. Includes severity, CVSS, KEV flag, fix version, direct vs. transitive. Use to assign fix ownership to engineering leads.
⚠ Fetch full data first for complete results
⚖ License Compliance
All unique licenses org-wide, tiered by legal risk (GPL/AGPL → LGPL/MPL → MIT/Apache). Ready to share with legal for approval/rejection workflow.
Source: Interlynk list_licenses (org-wide, no fetch needed)
📋 SBOM Coverage
All Bitbucket repos with their Interlynk import status — Active (scanning), Stale (SBOM not updated), Imported · No SBOM (added to Interlynk but no pipeline yet), or Not in Interlynk (never imported). Use for planning and audit evidence.
Source: Bitbucket + Interlynk join (no fetch needed)
💥 Blast Radius — CVE Impact
Unique CVEs ranked by how many products are affected. Fixing one CVE here removes risk across the most repos — highest ROI for engineering. Good for executive briefings.
⚠ Fetch full data first for complete results
🗂 Full CVE Inventory
Every CVE across every fetched product in one flat CSV — all severities, all teams. Use for audit evidence or feeding into a ticketing system.
Fetch full data first — this report combines all products.