Arnica
commercialThe section your link pointed to isn't on Arnica's page any more, so we've brought you to the top.
Arnica is an application security platform that scans code for vulnerabilities across SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment., SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself., IaCIaCInfrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup., and secrets, integrating directly into source code management.
Summary
Arnica is a commercial application security posture managementapplication security posture managementApplication security posture management, combining findings about applications from multiple tools and relating them to business context. It helps teams decide which fixes matter most. platform that protects developers, source code, and products across the software development lifecycle. It runs as a cloud-based service that connects into an organization's source control and CI/CD systems, covering SAST, SCA, IaC, open-source license violations, hardcoded secrets, and excessive developer access to code, with findings routed through chatops integrations like Microsoft Teams rather than a separate dashboard alone. It is aimed at application security and platform teams who need to manage risk across many repositories and contributors without slowing engineering down, offering an inventory of every person and service account with code access and a workflow for adjusting finding severity with a documented reason. It sits in the ASPMASPMApplication security posture management, combining findings about applications from multiple tools and relating them to business context. It helps teams decide which fixes matter most. category, consolidating code security, secrets detection, and supply-chain risk into one posture-management layer.
Arnica is an application security platform that scans code for vulnerabilities across SAST, SCA, IaC, and secrets, integrating directly into source code management.
How Arnica helps
Which service accounts and people have access to our code across every source control system we use?
builds a cross-SCM inventory of every human and service identity with repository access, so accounts scattered across different platforms show up in one place
Which of our repositories contain hardcoded secrets?
scans code for exposed credentials and tokens and reports where they live so they can be revoked and removed
Which of our open-source dependencies carry a known vulnerability?
checks the packages pulled into our codebase against known flaws and flags the ones exposed
Are any of our code changes introducing risk before they merge?
evaluates commits and pull requests against its checks so risky changes surface during review instead of after release
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 Arnica, 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 Arnica 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…
Commercials
pricing & packaging history · Arnica vendor page25 readings of Arnica's pricing page since May 2022, with 1 relaunch of its plan lineup and 15 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
arnica.io, every changeArnica's home, pricing and product pages and 40 more pages as they looked each month from October 2021 to October 2026: 55 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
3 entries
No entries match these filters.
- September 20263
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →