Workspace
Confirmed live
Last scan 2s ago
// FOR AI-NATIVE ENGINEERING TEAMS
CodeNSM is tracking CodeNSM · live
See which parts of your codebase are load-bearing, fragile, or quietly rotting — and who owns them — without reading every diff. CodeNSM turns every function into a code employee with a role and a health state, so you catch AI-generated technical debt before it pages you.
One pip install, names-only by default — your source never leaves your machine. Automated Tech Lead judgment for the LLM-coding era.
// takes 10 mins · no source upload · see your risk profile immediately · no card · cancel anytime
CISO-Ready · 0% source exposure (names-only mode)
// live proof
Every number on this page is CodeNSM running its own SDK on its own production codebase — so before you trust it on your code, you can watch it work on ours. Public proof, private architecture.
Workspace
Confirmed live
Last scan 2s ago
Staff roster
786 employees
5 archetypes on the floor
Health
69% Fit
6% stressed · 18% snoozing · 5% external
Architecture drift
Down 2.3%
7-day trend · improving
Privacy boundary
Source transmitted 0
Derived signals only
Recent safe event
Trust-path stress detected
Details redacted
Live telemetry from CodeNSM's own workspace — aggregated, rounded, delayed & redacted. transmit_raw_source=false
// the problem
Velocity is up. Architectural clarity is down. Modules land in minutes, but nobody can tell load-bearing from disposable — or which AI-written function is a fragile trust-path liability. The gap hits two people differently.
If you're the founder
You're shipping features and hitting your roadmap — but you can't see the structural integrity underneath. You have no way to judge whether the codebase is getting stronger or more brittle, so you wait for an incident to tell you that debt quietly became a liability.
If you're the engineer
You're responsible for a growing mountain of AI-generated functions you never authored — impossible to hold in your head, painful to debug, and slow to audit. When something breaks, you don't know which path carries the risk until you're already in it.
// the tools you have show files, folders and diffs — not which function is fragile, load-bearing, or rotting.
// cost of inaction
// the mechanism
Most tools force a bad trade: name-only scanners see no structure, and deep analyzers demand your whole repo. CodeNSM does neither. It derives structure locally with the standard-library AST and transmits only names + derived signals — a digital X-ray for your AI architecture that reads behavioral health, never raw source. We map every function so that you can see the brittle path so that it never pages you on a weekend.
structural preview approximates the local SDK's AST pass — not the exact production classifier
What CodeNSM derives and transmits
Elevated branching + retry pressure on a trust path. Review first.
What never leaves your machine
This ran entirely in your browser. In names-only mode only the derived signals above — never your source — would be transmitted.
Traditional tools show
CodeNSM shows
// source-safe by design
Two SDK depths keep your source on your machine. One optional connector — GitHub — is the single place you can grant code access, and only if you want commit-level ROI. You choose the line.
Names-Only Mode · recommended default
Zero code leaves your machine.
Allowed off-machine
Blocked
local → derived signals → dashboard
Local Full-Code Mode
Deeper analysis. Still local.
Control-flow shape is extracted on your machine with the standard-library ast. Only the shape — decisions, loops, call edges — ships. Never the source.
Stays local
mode="full" · local AST only
Connect GitHub · optional, you grant it
The only door to your code.
Everything above is derived on your machine — no repo access. Link GitHub and you give CodeNSM read access to your repository, so it can join commits to functions and price engineering time (commit-level ROI). This is the one place code leaves your world, and only because you opened the door.
You’re granting
Unlocks
optional · revoke in GitHub anytime
// how it works
$ pip install https://thinknorth.consulting/static/codensm/dist/codensm-1.0.0-py3-none-any.whl
# then, at startup:
>>> codensm.init(ingest_key="…", endpoint="…/codensm/ingest")
>>> codensm.autowatch("myapp")
Python shown. Node, PHP and Java ship the same five-outcome protocol with their own idiomatic SDK — codensm scan in CI, auto-instrumentation, or a decorator. Every way to wire each language in →
// takes 10 mins · no source upload · see your risk profile immediately · cancel anytime
// more proof · production
codensm/self · confirmed live
The same product surface used everywhere on this page is generated from CodeNSM running its own SDK on its own production code. If the product works, you are looking at it working — on itself.
Open Public-Safe Live Workspace →// view-only · public-safe · architecture-redacted · no sign-up
// more proof · the aha
Select an employee — the inspector explains why it matters and what to do. This is the same product surface, running public-safe. We rank by risk so that your attention lands on the function that carries it.
| Employee | Archetype | State | Workload | Latency | Value Path | Next Action |
|---|---|---|---|---|---|---|
| billing.fn_•••2c | Specialist Engineer | Top Performer | High | Fast | Revenue | Protect |
| auth.fn_•••7a | Security & Compliance | Stressed | Medium | Elevated | Trust | Review |
| notify.fn_•••4f | External Liaison | Network Latency | High | Slow | Comms | Check retries |
| parse.fn_•••91 | Records Clerk | Snoozing | Low | Fast | Ops | Leave |
| release.fn_•••a8 | Floor Supervisor | Fit | Medium | Normal | Release | Monitor |
// more proof · the platform
office.map() Virtual Office
The floor plan of your company — glowing employees, connector lines between value paths, aliases redacted. Watch load move in real time.
nsm.trace() North-Star Metric
Revenue · Trust · Ops · Release
staff.roster() Employee Roster
| Employee | State | Priority |
|---|---|---|
| billing.fn_•••2c | Top | Protect |
| auth.fn_•••7a | Stressed | Review |
| parse.fn_•••91 | Snoozing | Leave |
flow.render() Flow View
Node-link map of a request. Stressed node flags amber.
commit.align() GitHub Alignment
Link PR clusters to the value paths they actually moved.
fix.prompt() AI-Ready Fix Prompts
A repair prompt for your worst function — paste straight into your agent.
standup.check() Cadence
The standup, made falsifiable. Every prediction in the room checked against the commit log and the telemetry — not against who sounded most certain. Blockers, unplanned work, and each developer's calibration by area, with the denominators.
sdk.any() Four Languages
One five-outcome protocol, four first-party SDKs. A test that throws isn't an outage; a declared 404 isn't a failure — only a real escape counts.
Founder View
Tech Lead View
ALERT · trust path
auth.fn_•••7a crossed retry-pressure threshold. Debt trajectory ↑.
AI-Native Safety View
generated module · review
2 brittle · 4 solid paths
// access paths
Start Free
For teams ready to instrument their own app.
no card · 10-min setup
Watch Live Demo
For anyone who wants to see it before installing.
no sign-up required
Join Product Updates
For teams tracking the roadmap.
unsubscribe anytime
// no pricing commitments shown
// nothing to lose by looking
transmit_raw_source=false.// the questions engineering teams ask first
No. In names-only mode, only function names and counters leave your machine. In local full-code mode, control-flow shape is extracted locally via the standard-library AST and only that shape ships. Your raw source never leaves your infrastructure.
It classifies every function — including the ones your AI wrote — into an archetype and a live health state, then flags the fragile, load-bearing paths first. You see which AI-generated functions are brittle before they bite, so you can manage AI technical debt instead of meeting it during an incident.
Yes. The Founder view is a codebase health dashboard for non-technical founders: one North-Star Metric and a staff roster you can read without opening a file — so you can judge engineering and see where structural risk is accumulating without reading code.
No. CodeNSM points your team at the few functions that carry the most risk instead of every diff, and the SDK only records lightweight names and counters — no heavy runtime overhead. It's built to save review time, not add process.
That's exactly what it's for. CodeNSM doesn't care who wrote a function — it observes how each one behaves and how complex it is, which is precisely the visibility teams lose when AI ships code faster than anyone can reason about it.
You pip install the SDK, add one init call and choose a mode. Within about ten minutes your staff roster and North-Star Metric go live, your first stressed path is surfaced, and you get an AI-ready fix prompt for your worst function. No card, cancel anytime.
// see your own codebase
Start free in about ten minutes, or join the telemetry digest if you're not ready to install. Either way, your source stays exactly where it is.
takes 10 mins · no source upload · see your risk profile immediately · no card · cancel anytime