Noma Security
commercialThe section your link pointed to isn't on Noma Security's page any more, so we've brought you to the top.
Noma Security discovers an enterprise's AI applications and agents, manages their posture and protects them at runtime with compliance reporting.
Summary
Noma Security is a commercial ai-security platform that discovers an enterprise's AI applications and agents, manages their posture, and protects them at runtime while generating compliance reports. It does not specify deployment method, but it is for organizations concerned with agentic ai-security and ai-supply-chain risk. Its documentation places it alongside general ai-security monitoring solutions, and it was launched in 2023.
Noma Security discovers an enterprise's AI applications and agents, manages their posture and protects them at runtime with compliance reporting.
How Noma Security helps
Which AI applications and agents are actually running across the organization?
inventories AI usage across the environment and surfaces shadow deployments nobody registered with security
Which of our deployed agents have a posture problem before something exploits it?
evaluates configuration and exposure of discovered AI applications against a set of posture checks and flags the ones out of line
What happens when an AI agent misbehaves or gets attacked while it's running?
watches agent behavior at runtime and intervenes when it detects an attack or anomalous action
Where did the components in our AI supply chain come from, and can we trust them?
traces the models, packages and data sources feeding each AI application to expose supply-chain risk
Can we show an auditor what our AI risk posture looks like right now?
turns the discovered inventory and posture findings into compliance reports without extra manual collection
Which team owns a given AI application when an incident hits it?
ties each discovered agent back to the application it belongs to so responders know where to act
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Noma Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Noma Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
1 entry
No entries match these filters.
- September 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.