Public report of newrelic/newrelic-ruby-agent, published 6 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 6 November 2026, 11:03 UTC · Survey ID cd_30ed5809519f4a6cbe4ca2093c25a6f1
newrelic/newrelic-ruby-agent
Measured 6 November 2026, 11:02 UTC, at code version 38a1e89
Test reliability is not measured: The JS/TS suite's lockfile was refused.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 4 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 40,774 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Maturity, 45
Findings by how serious they are
16 critical252 serious106 minor
8 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
6 November 2026, 11:02 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
65of 65 dimensions measured by tools.
351of 374 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
65dimensions across 5 lenses, read from 40,774 lines of product code in 2 projects.
newrelic/newrelic-ruby-agent falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram, and the documentation refers to three links that don't exist. It scores 50 out of 100 and is rated Adequate, and 14 of its 16 critical findings are security problems.
Maturity, at 45, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 7 points. Recording design decisions would lift Maturity itself, worth about 5 points. Raising Maturity to 70 would lift the score to about 56.
Three passwords or keys are open to anyone who can read the repository. Three secrets can leak from the build pipeline, and two pipeline steps install packages that can change without warning. Replacing each exposed password or key, limiting each secret to its own step and pinning what the pipeline installs would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two places where the code runs text as code or as a command need a direct call instead. The two test suites that won't install need their lockfile updated so they install.
The product code is 40,774 lines, about €110,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
€37,000 to €190,000, for 624 to 1,978 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 40,774 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Raises the score by about 4 points · Medium effort · DR & Backup
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Maturity, at 45 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 1 Documentation Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
145 modules, with 75 dependencies between them. One loop runs through 5 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 105 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
NewRelic.Agent.Agent uses NewRelic.Agent, so a change to NewRelic.Agent can break NewRelic.Agent.Agent, while a change to NewRelic.Agent.Agent can't break NewRelic.Agent.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NewRelic.Agent.Database uses NewRelic, so a change to NewRelic can break NewRelic.Agent.Database, while a change to NewRelic.Agent.Database can't break NewRelic.
Position
Below the diagonal: NewRelic.Agent.Database uses a module listed above it, which is the healthy direction.
8→15 NewRelic.Agent.DistributedTracing uses NewRelic.Agentpart of a loop✕
Connections
1 pair of types, where a type in NewRelic.Agent.DistributedTracing uses a type in NewRelic.Agent.
NewRelic.Agent.DistributedTracing uses NewRelic.Agent, so a change to NewRelic.Agent can break NewRelic.Agent.DistributedTracing, while a change to NewRelic.Agent.DistributedTracing can't break NewRelic.Agent.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NewRelic.Agent.Instrumentation.Ethon.Easy uses NewRelic.Agent.Instrumentation.Ethon, so a change to NewRelic.Agent.Instrumentation.Ethon can break NewRelic.Agent.Instrumentation.Ethon.Easy, while a change to NewRelic.Agent.Instrumentation.Ethon.Easy can't break NewRelic.Agent.Instrumentation.Ethon.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Ethon.Easy uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Ethon.Multi uses NewRelic.Agent.Instrumentation.Ethon, so a change to NewRelic.Agent.Instrumentation.Ethon can break NewRelic.Agent.Instrumentation.Ethon.Multi, while a change to NewRelic.Agent.Instrumentation.Ethon.Multi can't break NewRelic.Agent.Instrumentation.Ethon.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Ethon.Multi uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.GRPC.Client uses NewRelic.Agent.Instrumentation.GRPC, so a change to NewRelic.Agent.Instrumentation.GRPC can break NewRelic.Agent.Instrumentation.GRPC.Client, while a change to NewRelic.Agent.Instrumentation.GRPC.Client can't break NewRelic.Agent.Instrumentation.GRPC.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.GRPC.Client uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.GRPC.Server uses NewRelic.Agent.Instrumentation.GRPC, so a change to NewRelic.Agent.Instrumentation.GRPC can break NewRelic.Agent.Instrumentation.GRPC.Server, while a change to NewRelic.Agent.Instrumentation.GRPC.Server can't break NewRelic.Agent.Instrumentation.GRPC.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.GRPC.Server uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Threading uses NewRelic, so a change to NewRelic can break NewRelic.Agent.Threading, while a change to NewRelic.Agent.Threading can't break NewRelic.
Position
Below the diagonal: NewRelic.Agent.Threading uses a module listed above it, which is the healthy direction.
13→15 NewRelic.Agent.Threading uses NewRelic.Agentpart of a loop✕
Connections
1 pair of types, where a type in NewRelic.Agent.Threading uses a type in NewRelic.Agent.
NewRelic.Agent.Threading uses NewRelic.Agent, so a change to NewRelic.Agent can break NewRelic.Agent.Threading, while a change to NewRelic.Agent.Threading can't break NewRelic.Agent.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
NewRelic.Agent.Commands uses NewRelic.Agent.Threading, so a change to NewRelic.Agent.Threading can break NewRelic.Agent.Commands, while a change to NewRelic.Agent.Commands can't break NewRelic.Agent.Threading.
Position
Below the diagonal: NewRelic.Agent.Commands uses a module listed above it, which is the healthy direction.
NewRelic.Agent uses NewRelic.Agent.AgentHelpers, so a change to NewRelic.Agent.AgentHelpers can break NewRelic.Agent, while a change to NewRelic.Agent can't break NewRelic.Agent.AgentHelpers.
Position
Below the diagonal: NewRelic.Agent uses a module listed above it, which is the healthy direction.
NewRelic.Agent uses NewRelic.Agent.ContinuousProfiling, so a change to NewRelic.Agent.ContinuousProfiling can break NewRelic.Agent, while a change to NewRelic.Agent can't break NewRelic.Agent.ContinuousProfiling.
Position
Below the diagonal: NewRelic.Agent uses a module listed above it, which is the healthy direction.
NewRelic.Agent uses NewRelic.Agent.Agent, so a change to NewRelic.Agent.Agent can break NewRelic.Agent, while a change to NewRelic.Agent can't break NewRelic.Agent.Agent.
Position
Below the diagonal: NewRelic.Agent uses a module listed above it, which is the healthy direction.
NewRelic.Agent uses NewRelic.Agent.DistributedTracing, so a change to NewRelic.Agent.DistributedTracing can break NewRelic.Agent, while a change to NewRelic.Agent can't break NewRelic.Agent.DistributedTracing.
Position
Below the diagonal: NewRelic.Agent uses a module listed above it, which is the healthy direction.
NewRelic.Agent uses NewRelic.Agent.Commands, so a change to NewRelic.Agent.Commands can break NewRelic.Agent, while a change to NewRelic.Agent can't break NewRelic.Agent.Commands.
Position
Below the diagonal: NewRelic.Agent uses a module listed above it, which is the healthy direction.
ActiveMerchant.Billing uses NewRelic.Agent, so a change to NewRelic.Agent can break ActiveMerchant.Billing, while a change to ActiveMerchant.Billing can't break NewRelic.Agent.
Position
Below the diagonal: ActiveMerchant.Billing uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation uses NewRelic.Agent, so a change to NewRelic.Agent can break NewRelic.Agent.Instrumentation, while a change to NewRelic.Agent.Instrumentation can't break NewRelic.Agent.
Position
Below the diagonal: NewRelic.Agent.Instrumentation uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Curb uses NewRelic.Agent, so a change to NewRelic.Agent can break NewRelic.Agent.Instrumentation.Curb, while a change to NewRelic.Agent.Instrumentation.Curb can't break NewRelic.Agent.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Curb uses a module listed above it, which is the healthy direction.
ActionController uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break ActionController, while a change to ActionController can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: ActionController uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.ActiveSupportBroadcastLogger uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.ActiveSupportBroadcastLogger, while a change to NewRelic.Agent.Instrumentation.ActiveSupportBroadcastLogger can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.ActiveSupportBroadcastLogger uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.ActiveSupportLogger uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.ActiveSupportLogger, while a change to NewRelic.Agent.Instrumentation.ActiveSupportLogger can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.ActiveSupportLogger uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.AsyncHttp uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.AsyncHttp, while a change to NewRelic.Agent.Instrumentation.AsyncHttp can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.AsyncHttp uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.AwsSdkLambda uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.AwsSdkLambda, while a change to NewRelic.Agent.Instrumentation.AwsSdkLambda can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.AwsSdkLambda uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.AwsSqs uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.AwsSqs, while a change to NewRelic.Agent.Instrumentation.AwsSqs can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.AwsSqs uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Bunny uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Bunny, while a change to NewRelic.Agent.Instrumentation.Bunny can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Bunny uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.ConcurrentRuby uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.ConcurrentRuby, while a change to NewRelic.Agent.Instrumentation.ConcurrentRuby can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.ConcurrentRuby uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Curb.Easy uses NewRelic.Agent.Instrumentation.Curb, so a change to NewRelic.Agent.Instrumentation.Curb can break NewRelic.Agent.Instrumentation.Curb.Easy, while a change to NewRelic.Agent.Instrumentation.Curb.Easy can't break NewRelic.Agent.Instrumentation.Curb.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Curb.Easy uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Curb.Multi uses NewRelic.Agent.Instrumentation.Curb, so a change to NewRelic.Agent.Instrumentation.Curb can break NewRelic.Agent.Instrumentation.Curb.Multi, while a change to NewRelic.Agent.Instrumentation.Curb.Multi can't break NewRelic.Agent.Instrumentation.Curb.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Curb.Multi uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.DelayedJob uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.DelayedJob, while a change to NewRelic.Agent.Instrumentation.DelayedJob can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.DelayedJob uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.DynamoDB uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.DynamoDB, while a change to NewRelic.Agent.Instrumentation.DynamoDB can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.DynamoDB uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Elasticsearch uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Elasticsearch, while a change to NewRelic.Agent.Instrumentation.Elasticsearch can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Elasticsearch uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Firehose uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Firehose, while a change to NewRelic.Agent.Instrumentation.Firehose can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Firehose uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.HTTPX uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.HTTPX, while a change to NewRelic.Agent.Instrumentation.HTTPX can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.HTTPX uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.HTTPrb uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.HTTPrb, while a change to NewRelic.Agent.Instrumentation.HTTPrb can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.HTTPrb uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Kinesis uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Kinesis, while a change to NewRelic.Agent.Instrumentation.Kinesis can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Kinesis uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.LogStasher uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.LogStasher, while a change to NewRelic.Agent.Instrumentation.LogStasher can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.LogStasher uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Logger uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Logger, while a change to NewRelic.Agent.Instrumentation.Logger can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Logger uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Roda uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Roda, while a change to NewRelic.Agent.Instrumentation.Roda can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Roda uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Sinatra uses NewRelic.Agent.Instrumentation, so a change to NewRelic.Agent.Instrumentation can break NewRelic.Agent.Instrumentation.Sinatra, while a change to NewRelic.Agent.Instrumentation.Sinatra can't break NewRelic.Agent.Instrumentation.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Sinatra uses a module listed above it, which is the healthy direction.
NewRelic.Agent.Instrumentation.Bunny.Prepend uses NewRelic.Agent.Instrumentation.Bunny, so a change to NewRelic.Agent.Instrumentation.Bunny can break NewRelic.Agent.Instrumentation.Bunny.Prepend, while a change to NewRelic.Agent.Instrumentation.Bunny.Prepend can't break NewRelic.Agent.Instrumentation.Bunny.
Position
Below the diagonal: NewRelic.Agent.Instrumentation.Bunny.Prepend uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 63% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
41
High / Critical
A02:2025 — Security Misconfiguration
12
High / Critical
A03:2025 — Software Supply Chain Failures
8
Medium
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Reconcile the README with reality: .github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/gem_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/gem_notifier.rb` does not exist; .github/workflows/scripts/slack_notifications/README.md links to `REDACTED`, but `.github/workflows/scripts/slack_notifications/REDACTED` does not exist; .github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/slack_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/slack_notifier.rb` does not exist.
Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
Set `open_timeout` and `read_timeout` explicitly on every client (Net::HTTP, Faraday `request: { timeout: }`, HTTParty `timeout:`), add Faraday's `:retry` middleware (faraday-retry) or `retriable`, and a breaker (`circuitbox`, `stoplight`) around dependencies that fail.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 16
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 252
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 106
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 65 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 351 of 374 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — app Pulling app Warning pull access denied for newrelic_rpm, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: failed to register layer: write /usr/lib/x86_64-linux-gnu/libicudata.a: no space left on device; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sequel' is imported (lib/sequel/plugins/new_relic_instrumentation.rb:6), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sequel' is imported (lib/sequel/plugins/new_relic_instrumentation.rb:6), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sequel' is imported (lib/sequel/plugins/new_relic_instrumentation.rb:6), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'sequel' is imported (lib/sequel/plugins/new_relic_instrumentation.rb:6), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a REDACTED ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was requireCore at 50. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DynamoDB.instrument_method_with_new_relic at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: lib/new_relic/agent/instrumentation/dynamodb/instrumentation.rb (DynamoDB.instrument_method_with_new_relic at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
requireCore (cyclomatic 50)REDACTED:2277
sprintf_format (cyclomatic 50)REDACTED:88356
fetch (cyclomatic 45)REDACTED:84939
constructor (cyclomatic 38)REDACTED:84708
parsePath (cyclomatic 35)REDACTED:82841
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 25 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with requireCore (cyclomatic 50), sprintf_format (cyclomatic 50), fetch (cyclomatic 45). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 25 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
44 method(s) exceeded the cognitive complexity threshold of 15; the worst was sprintf_format at 105.
constructor (cognitive 35) · ×2REDACTED:84226
sprintf_format (cognitive 105)REDACTED:88356
parseIPv6 (cognitive 75)REDACTED:82035
fetch (cognitive 63)REDACTED:84939
getValues (cognitive 58)REDACTED:3085
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with sprintf_format (cognitive 105), parseIPv6 (cognitive 75), fetch (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 10 TooManyMethods finding(s) in God Classes — start with REDACTED, new_relic_service.rb, manager.rb. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 4 FileTooLong finding(s) in God Classes — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Duplicated block (15–16 lines × 2) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with prepend.rb. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
2 production modules (RubyGems), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with agent.rb, REDACTED, log_event_aggregator.rb. — One of this dimension's main actionable groups (5 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 93.1% — read from a committed simplecov report (.github/actions/simplecov-report/dummy_coverage/.last_run.json); the in-image collector couldn't run the suite (commonly external-service dependencies). A real measurement, but from a committed artifact rather than a fresh in-image run.
Coverage read from a committed report
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
0 outdated direct gem(s), 1 pinning defect(s). 289 declaration(s) graded against rubygems.org, none of them against a committed REDACTED.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. 116 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. 289 of 291 gradable declaration(s) were graded against rubygems.org (0 not published there, 2 carrying a version or requirement this pass cannot order). Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Floating git dependency: rails
What to do
Resolve the 1 Floating git dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 32 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 32 runtime gem(s) this repository declares. It commits no REDACTED.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/new_relic/agent/continuous_profiling/session.rb. Counted over 187 of the 530 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)
What to do
Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
54 deducted task-comment markers across 40774 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 53 TodoComment finding(s) in Explicit Debt — start with sidekiq_test_helpers.rb (6), sidekiq_ignore_retry_errors_enabled_test.rb (4), parameter_capture_test.rb (3). — One of this dimension's main actionable groups (53 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with method_visibility_test.rb. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F4 map. 15 document(s) read across 4 unit(s).
Documentation: no map of the repository's partsREADME.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (Bundler) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
41 finding(s): 0 critical, 10 high, 31 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `REDACTED` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no REDACTED.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (2). — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
68 of 187 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 187 of the 530 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×68REDACTED:1
Orphaned files with no living knowledge
What to do
Resolve the 68 Orphaned file finding(s) in Knowledge Freshness — start with new_relic_instrumentation.rb (2), REDACTED (2), chain.rb (2). — One of this dimension's main actionable groups (68 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with chat_completion_summary.rb, tracer.rb, session.rb. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with stack_prof_sampler.rb. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 3 end-of-life framework(s), read from 0 platform declaration(s) and 291 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
End-of-life framework: Rails 4 · ×3REDACTED:1
What to do
Resolve the 3 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue in this repository's Ruby: methods whose whole body still raises NotImplementedError where nothing overrides them, or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Ruby: methods that only raise NotImplementedError or a "not implemented" error where nothing overrides them, methods that take inputs and return a constant or do nothing, dead `if false` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
113 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
.github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/gem_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/gem_notifier.rb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .github/workflows/scripts/slack_notifications/README.md:25
.github/workflows/scripts/slack_notifications/README.md links to `REDACTED`, but `.github/workflows/scripts/slack_notifications/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .github/workflows/scripts/slack_notifications/README.md:28
.github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/slack_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/slack_notifier.rb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .github/workflows/scripts/slack_notifications/README.md:29
What to do
Reconcile the README with reality: .github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/gem_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/gem_notifier.rb` does not exist; .github/workflows/scripts/slack_notifications/README.md links to `REDACTED`, but `.github/workflows/scripts/slack_notifications/REDACTED` does not exist; .github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/slack_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/slack_notifier.rb` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 58159 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `bundler`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:3
What to do
Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `npm`, `bundler` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×14) — lib/new_relic/agent/instrumentation/ethon.rb:17, lib/new_relic/agent/instrumentation/typhoeus.rb:13, lib/new_relic/agent/instrumentation/typhoeus.rb:17, …
`Excon.` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — lib/new_relic/agent/instrumentation/excon.rb:45
What to do
Set `open_timeout` and `read_timeout` explicitly on every client (Net::HTTP, Faraday `request: { timeout: }`, HTTParty `timeout:`), add Faraday's `:retry` middleware (faraday-retry) or `retriable`, and a breaker (`circuitbox`, `stoplight`) around dependencies that fail.
Other · Security — Read from this repository's Ruby source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for Ruby: this reading covers the code's own cryptography and the TLS connections it opens as a client, and a Rails, Rack or Sinatra application's transport, header and validation settings are not modelled. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — REDACTED:329, REDACTED:332
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `REDACTED:329` (Digest::SHA1.hexdigest), `REDACTED:332` (Digest::SHA1.hexdigest). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.2 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`normalize_params` is public and takes `params` — which it walks as a `Hash` — from its caller, and it calls itself at line 19 (`self.normalize_params`) with a piece of `params` (and at line 29) — and nowhere in `normalize_params` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `normalize_params` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/new_relic/collection_helper.rb:19
`normalize_object` is public and takes `object` — which it walks as a `Hash` — from its caller, and it calls itself at line 23 (`self.normalize_object`) with a piece of `object` (and at line 31) — and nowhere in `normalize_object` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `normalize_object` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/new_relic/agent/encoding_normalizer.rb:23
`obfuscate_value` is public and takes `value` — which it walks as a `Hash` — from its caller, and it calls itself at line 33 (`self.obfuscate_value`) with a piece of `value` — and nowhere in `obfuscate_value` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `obfuscate_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/new_relic/agent/datastores/nosql_obfuscator.rb:33
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 138 is called with an argument built by `caller.join("\n")` (line 138), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent.rb:138
`debug` at line 129 is called with an argument built by `messages.join(',')` (line 129), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent/error_filter.rb:129
`debug` at line 139 is called with an argument built by `messages.join(',')` (line 139), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent/error_filter.rb:139
`debug` at line 203 is called with an argument built by `custom_attributes.keys` (line 204), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent/javascript_instrumentor.rb:203
`debug` at line 38 is called with an argument built by `event_names.join(', ')` (line 38), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent/instrumentation/rails_event_logger.rb:38
`debug` at line 63 is called with an argument built by `unmapped_otel_keys.join(', ')` (line 65), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent/configuration/open_telemetry_source.rb:63
`debug` at line 91 is called with an argument built by `profile_descriptions.join(', ')` (line 91), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/new_relic/agent/commands/agent_command_router.rb:91
What to do
In Ruby, hand the logger a block it calls only when the level is on (`logger.debug { "args: #{args.join(' ')}" }` — Logger, ActiveSupport, SemanticLogger and console all take one), or put the line behind `if logger.debug?`. Interpolating the value into the message is not the fix: Ruby builds the string, and every `map`, `join` or `to_json` inside its `#{…}`, before the call is entered.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — REDACTED:66, lib/new_relic/agent/database.rb:235, lib/new_relic/agent/database.rb:245, …
`… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — lib/new_relic/local_environment.rb:87, lib/new_relic/local_environment.rb:94, lib/new_relic/agent/agent_logger.rb:143, …
`rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×10) — lib/new_relic/agent/log_event_aggregator.rb:91, lib/new_relic/agent/log_event_aggregator.rb:117, lib/new_relic/agent/log_event_aggregator.rb:140, …
`rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — lib/new_relic/agent/transaction_time_aggregator.rb:119
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 528 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'sequel' (lib/sequel/plugins/new_relic_instrumentation.rb:6) but declares no persisted model this check reads (ActiveRecord and Sequel migration columns, db/schema.rb, Mongoid document fields). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'sequel' (lib/sequel/plugins/new_relic_instrumentation.rb:6) but declares no persisted model this check reads (ActiveRecord/Sequel migration and db/schema.rb columns, Mongoid document fields). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'sequel' (lib/sequel/plugins/new_relic_instrumentation.rb:6) but declares no persisted model this check reads (ActiveRecord migration and db/schema.rb columns, Sequel migration columns, Mongoid fields). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — app Pulling app Warning pull access denied for newrelic_rpm, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: failed to register layer: write /usr/lib/x86_64-linux-gnu/libicudata.a: no space left on device; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: this repository stores data through 'sequel' (lib/sequel/plugins/new_relic_instrumentation.rb:6) but declares no persisted model this check reads (ActiveRecord migration and db/schema.rb columns, Sequel migration columns, Mongoid fields). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository draws no route and defines no request handler (no Rails routes.draw or controller, no Sinatra, Roda or Grape application, no Hanami action). Access control is therefore N/A here — a gem is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — ~78960 lines of test source are present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for .github/actions/simplecov-report/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python, Ruby, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rb source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D9 Test Distribution — Test source is present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 17 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a REDACTED or gemspec, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: Ruby runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
PF3 Async & latency hygiene — Not applicable: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
D11 · Test Reliability· Test suite cannot be installed from its own lockfile · ×2
Test suite cannot be installed from its own lockfile: .github/actions/simplecov-report/ — The jest suite in .github/actions/simplecov-report/ was never exercised because its dependency install refused the committed lockfile — the dependency install for .github/actions/simplecov-report/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: .github/actions/variable-mapper/ — The jest suite in .github/actions/variable-mapper/ was never exercised because its dependency install refused the committed lockfile — the dependency install for .github/actions/variable-mapper/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
TodoComment test/new_relic/slack_notifications_test/gem_notifier_test.rb:15— # TODO: MAJOR VERSION - Remove this version constraint when we update the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/new_relic/slack_notifications_test/slack_notifier_test.rb:15— # TODO: MAJOR VERSION - Remove this version constraint when we update the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/new_relic/agent/datastores_test.rb:140— # TODO: MAJOR VERSION - this warning should be removed on our next major — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/new_relic/agent/tracer_test.rb:205— # TODO: Implement current_segment on Tracer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/new_relic/agent/instrumentation/rails/action_cable_subscriber.rb:259— # TODO: Remove when we no longer support Rails 5.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/new_relic/agent/instrumentation/rails/action_dispatch_subscriber.rb:128— # TODO: uncomment after the :disable_action_dispatch TODO comment in — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_ignore_retry_errors_enabled_test.rb:14— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_ignore_retry_errors_enabled_test.rb:38— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_ignore_retry_errors_enabled_test.rb:62— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_ignore_retry_errors_enabled_test.rb:80— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_test_helpers.rb:10— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_test_helpers.rb:50— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_ignore_retry_errors_disabled_test.rb:33— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_ignore_retry_errors_disabled_test.rb:57— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_instrumentation_test.rb:42— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_test_helpers.rb:10— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_test_helpers.rb:58— # TODO: MAJOR VERSION - remove this when Sidekiq v5 is no longer supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq_ignore_retry_errors_enabled/sidekiq_test_helpers.rb:59— # TODO: MAJOR VERSION - Sidekiq v7 is fine with launcher.stop, but v5 and v6 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_test_helpers.rb:67— # TODO: MAJOR VERSION - Sidekiq v7 is fine with launcher.stop, but v5 and v6 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/sidekiq/sidekiq_args_filtration_test.rb:72— # TODO: OLD RUBIES - Requires 3.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/rails/error_tracing_test.rb:293— # TODO: stop the flapping/flaking — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/rails/error_tracing_test.rb:369— # TODO: stop the flapping/flaking — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/rails/parameter_capture_test.rb:67— # TODO: stop the flapping/flaking — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/rails/parameter_capture_test.rb:90— # TODO: stop the flapping/flaking — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/multiverse/suites/rails/parameter_capture_test.rb:211— # TODO: stop the flapping/flaking — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Swallowed exception (caught, then discarded) lib/new_relic/local_environment.rb:87— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/local_environment.rb:94— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/agent_logger.rb:143— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/log_event_aggregator.rb:91— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/log_event_aggregator.rb:117— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/log_event_aggregator.rb:140— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/log_event_aggregator.rb:163— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/log_event_aggregator.rb:187— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/system_info.rb:73— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/transaction_time_aggregator.rb:119— `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/samplers/memory_sampler.rb:79— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/samplers/memory_sampler.rb:105— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/samplers/memory_sampler.rb:123— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/instrumentation/controller_instrumentation.rb:405— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/instrumentation/controller_instrumentation.rb:446— `… rescue nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/instrumentation/mongodb_command_subscriber.rb:30— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/instrumentation/sinatra/transaction_namer.rb:58— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/distributed_tracing/trace_context_payload.rb:119— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/new_relic/agent/configuration/manager.rb:146— `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/ethon.rb:17— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/excon.rb:45— `Excon.` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus.rb:13— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus.rb:17— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus.rb:26— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus.rb:27— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus.rb:38— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus.rb:40— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/chain.rb:6— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/chain.rb:9— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/chain.rb:10— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/instrumentation.rb:8— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/instrumentation.rb:15— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/prepend.rb:6— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/new_relic/agent/instrumentation/typhoeus/prepend.rb:8— `Typhoeus` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
TooManyMethods: Transaction REDACTED:23— TooManyMethods — 108 methods. The bar is 30 methods; this is 78 over it, 3.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NewRelicService lib/new_relic/agent/new_relic_service.rb:13— TooManyMethods — 81 methods. The bar is 30 methods; this is 51 over it, 2.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Manager lib/new_relic/agent/configuration/manager.rb:17— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LogEventAggregator lib/new_relic/agent/log_event_aggregator.rb:11— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Agent lib/new_relic/agent.rb:23— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Session lib/new_relic/agent/continuous_profiling/session.rb:13— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractSegment lib/new_relic/agent/transaction/abstract_segment.rb:10— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ErrorCollector REDACTED:12— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProfileEncoder lib/new_relic/agent/continuous_profiling/profile_encoder.rb:13— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ServerlessHandler lib/new_relic/agent/serverless_handler.rb:13— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: Agent (LCOM4 8) lib/new_relic/agent/agent.rb:58— Agent's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Transaction (LCOM4 5) REDACTED:23— Transaction's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LogEventAggregator (LCOM4 4) lib/new_relic/agent/log_event_aggregator.rb:11— LogEventAggregator's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Stats (LCOM4 4) lib/new_relic/agent/stats.rb:7— Stats's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AbstractSegment (LCOM4 4) lib/new_relic/agent/transaction/abstract_segment.rb:10— AbstractSegment's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
FileTooLong: REDACTED REDACTED— FileTooLong — 39474 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 38974 over it, 78.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 2697 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2197 over it, 5.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 784 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 284 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: agent/new_relic_service.rb lib/new_relic/agent/new_relic_service.rb— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Swallowed exception (empty catch) REDACTED:66— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/new_relic/agent/database.rb:235— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/new_relic/agent/database.rb:245— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:211— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Change coupling: chat_completion_summary.rb ↔ embedding.rb lib/new_relic/agent/llm/chat_completion_summary.rb:1— `lib/new_relic/agent/llm/chat_completion_summary.rb` and `lib/new_relic/agent/llm/embedding.rb` change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `819845bb` address old ruby todos; `cfadfeb9` Apply suggestions from code review; `7ffd1f6e` Remove outdated token-related attributes — run `git show` on any of them.
Change coupling: tracer.rb ↔ attribute_mappings.rb lib/new_relic/agent/opentelemetry/trace/tracer.rb:1— `lib/new_relic/agent/opentelemetry/trace/tracer.rb` and `lib/new_relic/agent/opentelemetry/translators/attribute_mappings.rb` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `65c10096` Address feedback, refactor; `8a7334d8` Mapping updates; `b214e8e3` Add mapping, translator, tests — run `git show` on any of them.
Change coupling: session.rb ↔ new_relic_service.rb lib/new_relic/agent/continuous_profiling/session.rb:1— `lib/new_relic/agent/continuous_profiling/session.rb` and `lib/new_relic/agent/new_relic_service.rb` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `e1efd45e` fix some small things; `2f8dce73` update comments; `7ec250d0` fix a few things — run `git show` on any of them.
End-of-life framework: Rails 4 REDACTED:1— REDACTED depends on `rails` at a version that pins Rails 4, and Rails 4, support ended 2017-04-27. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
End-of-life framework: Rails 5 test/environments/rails50/Gemfile:1— test/environments/rails50/Gemfile depends on `rails` at a version that pins Rails 5, and Rails 5, support ended 2022-06-01. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
End-of-life framework: Rails 6 test/environments/rails60/Gemfile:1— test/environments/rails60/Gemfile depends on `rails` at a version that pins Rails 6, and Rails 6, support ended 2024-10-01. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×3
JavaScript dependencies are not locked .github/actions/issue_closer/package.json:25— .github/actions/issue_closer/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked .github/actions/simplecov-report/package.json:28— .github/actions/simplecov-report/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked .github/actions/variable-mapper/package.json:25— .github/actions/variable-mapper/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×3
Recursive walk over a caller-supplied document has no depth cap lib/new_relic/collection_helper.rb:19— `normalize_params` is public and takes `params` — which it walks as a `Hash` — from its caller, and it calls itself at line 19 (`self.normalize_params`) with a piece of `params` (and at line 29) — and nowhere in `normalize_params` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `normalize_params` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap lib/new_relic/agent/encoding_normalizer.rb:23— `normalize_object` is public and takes `object` — which it walks as a `Hash` — from its caller, and it calls itself at line 23 (`self.normalize_object`) with a piece of `object` (and at line 31) — and nowhere in `normalize_object` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `normalize_object` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap lib/new_relic/agent/datastores/nosql_obfuscator.rb:33— `obfuscate_value` is public and takes `value` — which it walks as a `Hash` — from its caller, and it calls itself at line 33 (`self.obfuscate_value`) with a piece of `value` — and nowhere in `obfuscate_value` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `obfuscate_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
constructor (cognitive 35) REDACTED:84226— constructor has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 5 (14 pts), boolean chains 2, ternaries 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
constructor (cognitive 35) REDACTED:84708— constructor has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 16, if/else 9 (11 pts), ternaries 8 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Weak hash algorithm REDACTED:329— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm REDACTED:332— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
requireCore (cyclomatic 50) REDACTED:2277— requireCore has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 2 of the 50 points are its own statements and the rest belongs to 45 function items inside it that branch (a function literal at line 2280, a function literal at line 2293, (anonymous)::getInput, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
sprintf_format (cyclomatic 50) REDACTED:88356— sprintf_format has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
fetch (cyclomatic 45) REDACTED:84939— fetch has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 2 of the 45 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 85007, a function literal at line 84949, (anonymous)::abort, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
constructor (cyclomatic 38) REDACTED:84708— constructor has cyclomatic complexity 38 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parsePath (cyclomatic 35) REDACTED:82841— parsePath has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseIPv6 (cyclomatic 32) REDACTED:82035— parseIPv6 has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
requireSummary (cyclomatic 29) REDACTED:1918— requireSummary has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 35 function items inside it that branch (a function literal at line 2094, a function literal at line 1949, a function literal at line 1993, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseScheme (cyclomatic 27) REDACTED:82394— parseScheme has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
request (cyclomatic 26) REDACTED:1394— request has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 1395). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
_getAgent (cyclomatic 24) REDACTED:1611— _getAgent has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseHostName (cyclomatic 24) REDACTED:82625— parseHostName has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
v1 (cyclomatic 23) REDACTED:309— v1 has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
getValues (cyclomatic 23) REDACTED:3085— getValues has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
createNumberConversion (cyclomatic 21) REDACTED:3325— createNumberConversion has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 3335). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
fetchWrapper (cyclomatic 20) REDACTED:85368— fetchWrapper has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85389, 85452, 85444). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Manager.type_coerce (cyclomatic 19) lib/new_relic/agent/configuration/manager.rb:213— Manager.type_coerce has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
getNodeRequestOptions (cyclomatic 19) REDACTED:84828— getNodeRequestOptions has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ErrorFilter.load_from_config (cyclomatic 18) lib/new_relic/agent/error_filter.rb:27— ErrorFilter.load_from_config has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
requireOidcUtils (cyclomatic 18) REDACTED:1832— requireOidcUtils has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 1873, a function literal at line 1890, a function literal at line 1835, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
requirePathUtils (cyclomatic 18) REDACTED:2212— requirePathUtils has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseQuery (cyclomatic 18) REDACTED:82923— parseQuery has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
SpanEventPrimitive.for_datastore_segment (cyclomatic 17) lib/new_relic/agent/span_event_primitive.rb:100— SpanEventPrimitive.for_datastore_segment has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
parse (cyclomatic 17) REDACTED:3190— parse has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
encode (cyclomatic 17) REDACTED:3808— encode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
constructor (cyclomatic 16) REDACTED:84226— constructor has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: REDACTED holds 22 of the 25 methods over the threshold — including the worst — and 260 of the 269 points over it (97%), 65× the next-largest file (lib/new_relic/agent/configuration/manager.rb at 4). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D11 · Test Reliability· Test reliability not measured · ×1
Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for .github/actions/simplecov-report/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.
Floating git dependency: rails — Gem `rails` is declared in test/environments/railsedge/Gemfile from a git source (https://github.com/rails/rails.git) with no immutable pin — `main` is a branch, not a commit. Two `bundle install` runs of this commit can therefore install different code, and nothing in the repository records which revision a given build used. Pin it to a commit (`ref: "<sha>"`) or a release tag (`tag: "v1.2.3"`), or take the gem from rubygems.org if it publishes there.
FixmeComment test/new_relic/agent/method_visibility_test.rb:89— # FIXME: Currently including MethodTracer and ControllerInstrumentation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
sprintf_format (cognitive 105) REDACTED:88356— sprintf_format has cognitive complexity 105 (threshold 15). Drivers by points: ternaries 15 (61 pts), if/else 13 (31 pts), boolean chains 5, loops 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 69). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseIPv6 (cognitive 75) REDACTED:82035— parseIPv6 has cognitive complexity 75 (threshold 15). Drivers by points: if/else 23 (58 pts), loops 5 (12 pts), boolean chains 5 (nesting depth added 42). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
fetch (cognitive 63) REDACTED:84939— fetch has cognitive complexity 63 (threshold 15). Drivers by points: if/else 22 (37 pts), boolean chains 11, error handling 2 (6 pts), loops 1 (4 pts), ternaries 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 24). Most of this is not in the body itself: 1 of the 63 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 85007, a function literal at line 84949, (anonymous)::abort, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
getValues (cognitive 58) REDACTED:3085— getValues has cognitive complexity 58 (threshold 15). Drivers by points: if/else 19 (44 pts), ternaries 2 (8 pts), boolean chains 6 (nesting depth added 31). Of this number, 43 points are the body's own statements and 15 belong to 4 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
requireCore (cognitive 52) REDACTED:2277— requireCore has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 22, if/else 16 (18 pts), ternaries 8, error handling 2, loops 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 1 of the 52 points is its own statement and the rest belongs to 45 function items inside it that branch (a function literal at line 2280, a function literal at line 2293, (anonymous)::getInput, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
request (cognitive 47) REDACTED:1394— request has cognitive complexity 47 (threshold 15). Drivers by points: if/else 11 (29 pts), loops 5 (11 pts), boolean chains 6, ternaries 1 (nesting depth added 24). None of this is in the body itself: all 47 points belong to one function literal inside it that branches (line 1395). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parsePath (cognitive 47) REDACTED:82841— parsePath has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 18, loops 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
encode (cognitive 41) REDACTED:3808— encode has cognitive complexity 41 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 5 (10 pts), ternaries 2 (10 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseScheme (cognitive 39) REDACTED:82394— parseScheme has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (29 pts), boolean chains 10 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
sprintf_parse (cognitive 32) REDACTED:88467— sprintf_parse has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 2 (6 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
_getAgent (cognitive 31) REDACTED:1611— _getAgent has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 10, ternaries 4 (10 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
decode (cognitive 30) REDACTED:3717— decode has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 3 (8 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
requireSummary (cognitive 28) REDACTED:1918— requireSummary has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 12, ternaries 8, if/else 5, error handling 3. Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 35 function items inside it that branch (a function literal at line 2094, a function literal at line 1949, a function literal at line 1993, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseHostName (cognitive 28) REDACTED:82625— parseHostName has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 8 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parse (cognitive 26) REDACTED:3190— parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 7). Of this number, 23 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
SpanEventPrimitive.intrinsics_for (cognitive 25) lib/new_relic/agent/span_event_primitive.rb:140— SpanEventPrimitive.intrinsics_for has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (25 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
createNumberConversion (cognitive 25) REDACTED:3325— createNumberConversion has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 4, ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 3335). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
v1 (cognitive 23) REDACTED:309— v1 has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (8 pts), ternaries 3, loops 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
fetchWrapper (cognitive 22) REDACTED:85368— fetchWrapper has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 2 (3 pts), error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 85389, 85452, 85444). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Connect.connect (cognitive 21) lib/new_relic/agent/agent_helpers/connect.rb:186— Connect.connect has cognitive complexity 21 (threshold 15). Drivers by points: error handling 5 (15 pts), if/else 2 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseQuery (cognitive 21) REDACTED:82923— parseQuery has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
_processResponse (cognitive 20) REDACTED:1677— _processResponse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5, error handling 1 (nesting depth added 3). None of this is in the body itself: all 20 points belong to 4 function items inside it that branch (a function literal at line 1679, (anonymous)::(anonymous)::(anonymous)::dateTimeDeserializer, a function literal at line 1678, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
requirePathUtils (cognitive 20) REDACTED:2212— requirePathUtils has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 2227, a function literal at line 2215, a function literal at line 2218, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseAuthority (cognitive 20) REDACTED:82583— parseAuthority has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parseFileHost (cognitive 20) REDACTED:82779— parseFileHost has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Manager.type_coerce (cognitive 19) lib/new_relic/agent/configuration/manager.rb:213— Manager.type_coerce has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 7 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LogEventAggregator.add_rails_event_attributes (cognitive 19) lib/new_relic/agent/log_event_aggregator.rb:413— LogEventAggregator.add_rails_event_attributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Messaging.start_amqp_consume_segment (cognitive 19) lib/new_relic/agent/messaging.rb:247— Messaging.start_amqp_consume_segment has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseFile (cognitive 19) REDACTED:82711— parseFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
convertBody (cognitive 19) REDACTED:83956— convertBody has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
getNodeRequestOptions (cognitive 19) REDACTED:84828— getNodeRequestOptions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
serializeURL (cognitive 18) REDACTED:82975— serializeURL has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
createHeadersLenient (cognitive 18) REDACTED:84531— createHeadersLenient has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
toString (cognitive 17) REDACTED:149— toString has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
requireOidcUtils (cognitive 17) REDACTED:1832— requireOidcUtils has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 5, if/else 5, error handling 4, ternaries 3. Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 1873, a function literal at line 1890, a function literal at line 1835, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
(anonymous) (cognitive 17) REDACTED:3448— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
constructor (cognitive 17) REDACTED:83535— constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
graphql (cognitive 17) REDACTED:85547— graphql has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 5). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
SpanEventPrimitive.for_datastore_segment (cognitive 16) lib/new_relic/agent/span_event_primitive.rb:100— SpanEventPrimitive.for_datastore_segment has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
constructor (cognitive 16) REDACTED:1274— constructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
expand (cognitive 16) REDACTED:3156— expand has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 6). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 3158, 3166). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
parsePort (cognitive 16) REDACTED:82681— parsePort has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: REDACTED holds 38 of the 44 methods over the threshold — including the worst — and 599 of the 628 points over it (95%), 54.5× the next-largest file (lib/new_relic/agent/span_event_primitive.rb at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Change-coupling hub: stack_prof_sampler.rb → REDACTED, profile_encoder.rb, new_relic_service.rb lib/new_relic/agent/continuous_profiling/stack_prof_sampler.rb— `lib/new_relic/agent/continuous_profiling/stack_prof_sampler.rb` changes together with 3 other files — `REDACTED`, `lib/new_relic/agent/continuous_profiling/profile_encoder.rb`, `lib/new_relic/agent/new_relic_service.rb` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Duplicated block (15–16 lines × 2) lib/new_relic/agent/instrumentation/elasticsearch/instrumentation.rb:70— lib/new_relic/agent/instrumentation/elasticsearch/instrumentation.rb:70-85 | lib/new_relic/agent/instrumentation/opensearch/instrumentation.rb:16-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) lib/new_relic/agent/instrumentation/rdkafka/instrumentation.rb:36— lib/new_relic/agent/instrumentation/rdkafka/instrumentation.rb:36-50 | lib/new_relic/agent/instrumentation/ruby_kafka/instrumentation.rb:36-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:24— lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:24-36 | lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:92-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:24` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:47— lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:47-58 | lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:69-80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/new_relic/agent/instrumentation/grpc/client/prepend.rb:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) lib/new_relic/agent/instrumentation/fiber/instrumentation.rb:10— lib/new_relic/agent/instrumentation/fiber/instrumentation.rb:10-17 | lib/new_relic/agent/instrumentation/thread/instrumentation.rb:12-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/new_relic/agent/llm/chat_completion_summary.rb:48— lib/new_relic/agent/llm/chat_completion_summary.rb:48-54 | lib/new_relic/agent/llm/embedding.rb:42-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) lib/new_relic/agent/span_event_aggregator.rb:20— lib/new_relic/agent/span_event_aggregator.rb:20-29 | lib/new_relic/agent/transaction_event_aggregator.rb:20-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) lib/new_relic/agent/transaction/datastore_segment.rb:153— lib/new_relic/agent/transaction/datastore_segment.rb:153-160 | lib/new_relic/agent/transaction/external_request_segment.rb:124-130 | lib/new_relic/agent/transaction/segment.rb:90-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 113 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/attribute_filter.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/system_info.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/threading/backtrace_service.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/distributed_tracing/trace_context.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file bin/nrdebug:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/stats_engine.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/noticed_error.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/distributed_tracing.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/transaction/request_attributes.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/error_filter.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/control/frameworks/rails.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/logging.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/agent_logger.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/datastores/mongo/metric_translator.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file infinite_tracing/lib/infinite_tracing/client.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/instrumentation/active_record_subscriber.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file infinite_tracing/lib/infinite_tracing/streaming_buffer.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/stats_engine/stats_hash.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/transaction/trace_node.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/event_loop.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file infinite_tracing/lib/infinite_tracing/config.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/samplers/memory_sampler.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/attributes.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/new_relic/agent/instrumentation/rails3/action_controller.rb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate lib/new_relic/agent/new_relic_service/encoders.rb:30— `!opts[:skip_normalization] && Agent.config[:normalize_json_string_encodings]` appears character-identically in 2 files — lib/new_relic/agent/new_relic_service/encoders.rb, lib/new_relic/agent/new_relic_service/json_marshaller.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:137— `defined?(::Sinatra) && defined?(::Sinatra::Base)` appears character-identically in 2 files — REDACTED, lib/new_relic/agent/instrumentation/tilt/instrumentation.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/new_relic/agent/instrumentation/rails_notifications/action_controller.rb:13— `defined?(Rails::VERSION::MAJOR) && Rails::VERSION::MAJOR.to_i >= 4` appears character-identically in 2 files — lib/new_relic/agent/instrumentation/rails_notifications/action_controller.rb, lib/new_relic/agent/instrumentation/rails_notifications/action_view.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/new_relic/agent/transaction_error_primitive.rb:89— `k.to_s.start_with?('synthetics_') && !SYNTHETICS_PAYLOAD_EXPECTED.include?(k)` appears character-identically in 2 files — lib/new_relic/agent/transaction_error_primitive.rb, lib/new_relic/agent/transaction_event_primitive.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/new_relic/agent/instrumentation/elasticsearch/instrumentation.rb:92— `location && location.to_s =~ INSTANCE_METHOD_PATTERN` appears character-identically in 2 files — lib/new_relic/agent/instrumentation/elasticsearch/instrumentation.rb, lib/new_relic/agent/instrumentation/opensearch/instrumentation.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/new_relic/agent/new_relic_service.rb:146— `stats_hash.harvested_at || Process.clock_gettime(Process::CLOCK_REALTIME)` appears character-identically in 2 files — lib/new_relic/agent/new_relic_service.rb, lib/new_relic/agent/serverless_handler.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/new_relic/agent/instrumentation/elasticsearch/instrumentation.rb:118— `transport.hosts.first || NewRelic::EMPTY_HASH` appears character-identically in 2 files — lib/new_relic/agent/instrumentation/elasticsearch/instrumentation.rb, lib/new_relic/agent/instrumentation/opensearch/instrumentation.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×7
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent.rb:138— `debug` at line 138 is called with an argument built by `caller.join("\n")` (line 138), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent/error_filter.rb:129— `debug` at line 129 is called with an argument built by `messages.join(',')` (line 129), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent/error_filter.rb:139— `debug` at line 139 is called with an argument built by `messages.join(',')` (line 139), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent/javascript_instrumentor.rb:203— `debug` at line 203 is called with an argument built by `custom_attributes.keys` (line 204), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent/instrumentation/rails_event_logger.rb:38— `debug` at line 38 is called with an argument built by `event_names.join(', ')` (line 38), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent/configuration/open_telemetry_source.rb:63— `debug` at line 63 is called with an argument built by `unmapped_otel_keys.join(', ')` (line 65), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted lib/new_relic/agent/commands/agent_command_router.rb:91— `debug` at line 91 is called with an argument built by `profile_descriptions.join(', ')` (line 91), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 14 significant file(s) lose their only recent owner: lib/new_relic/agent/pipe_channel_manager.rb, lib/new_relic/agent/datastores.rb, lib/new_relic/agent/transaction/distributed_tracing.rb, lib/new_relic/agent/health_check.rb, lib/new_relic/agent/opentelemetry/trace/span.rb, lib/new_relic/agent/database/explain_plan_helpers.rb, lib/new_relic/agent/instrumentation/active_job.rb, lib/new_relic/agent/opentelemetry/translators/base_translator.rb (+6 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 12 significant file(s) lose their only recent owner: lib/new_relic/agent/continuous_profiling/session.rb, lib/new_relic/agent/database.rb, lib/new_relic/agent/continuous_profiling/profile_encoder.rb, lib/new_relic/agent/utilization_data.rb, lib/new_relic/agent/instrumentation/bunny/instrumentation.rb, lib/new_relic/agent/transaction/datastore_segment.rb, lib/new_relic/agent/datastores/metric_helper.rb, lib/new_relic/agent/instrumentation/middleware_tracing.rb (+4 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 8 significant file(s) lose their only recent owner: lib/new_relic/agent/javascript_instrumentor.rb, lib/new_relic/agent/opentelemetry/translators/messaging_translator.rb, lib/new_relic/agent/instrumentation/action_controller_subscriber.rb, lib/new_relic/agent/instrumentation/active_record_prepend.rb, lib/new_relic/agent/instrumentation/typhoeus/instrumentation.rb, lib/new_relic/agent/instrumentation/aws_sdk_kinesis/instrumentation.rb, lib/new_relic/agent/transaction/transaction_sample_buffer.rb, lib/new_relic/cli/command.rb. Pair on, review, or document these before any departure.
README/code drift .github/workflows/scripts/slack_notifications/README.md:25— .github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/gem_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/gem_notifier.rb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift .github/workflows/scripts/slack_notifications/README.md:28— .github/workflows/scripts/slack_notifications/README.md links to `REDACTED`, but `.github/workflows/scripts/slack_notifications/REDACTED` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift .github/workflows/scripts/slack_notifications/README.md:29— .github/workflows/scripts/slack_notifications/README.md links to `.github/workflows/scripts/slack_notifications/slack_notifier.rb`, but `.github/workflows/scripts/slack_notifications/.github/workflows/scripts/slack_notifications/slack_notifier.rb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (35 single-owned of 187 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 187 of the 530 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: lib/new_relic/agent/instrumentation/action_view_subscriber.rb.
Documentation: no map of the repository's parts README.md:1— The repository has 3 units (`issue_closer`, `simplecov-report`, `variable-mapper`); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (39777 LoC, 1572 module-visible types across 89 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 68 of 187 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 187 of the 530 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: REDACTED, lib/new_relic/agent/attribute_filter.rb, lib/new_relic/agent/system_info.rb, lib/new_relic/agent/threading/backtrace_service.rb, lib/new_relic/agent/distributed_tracing/trace_context.rb, bin/nrdebug, lib/new_relic/agent/stats_engine.rb, lib/new_relic/noticed_error.rb (and 60 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST REDACTED:3— No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 58159 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch npm/bundler · ×1
Dependabot does not watch npm/bundler REDACTED:3— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `bundler`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
X5 · Nullable reference types· Ruby's type checker does not check nil everywhere · ×1
Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 528 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Silent fallback default on parse failure .fleetControl/schemaGeneration/schema_diff.rb:32— `load_existing` answers `{}` when `ParserError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Minor — 1 finding(s)
D8 · Code Coverage· Coverage read from a committed report · ×1
Coverage read from a committed report — Line coverage 93.1% — read from a committed simplecov report (.github/actions/simplecov-report/dummy_coverage/.last_run.json); the in-image collector couldn't run the suite (commonly external-service dependencies). A real measurement, but from a committed artifact rather than a fresh in-image run.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1b086-1ccc-7aaf-8d34-83c635ff4a96 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 16 · Warnings: 252 · Recommendations: 105 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 06-11-2026 @ 11:02 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.