# Strategic Guide - Metrics

> This is the single source of truth for the numbers that describe KernDX: how much code it contains, how many tests run, how big the public API is, and how it compares on size and activity. Every other guide links here instead of repeating a figure, so there is only one place to keep current. If you are looking up a statistic to cite, this is the page. Update this file when the codebase changes.

Part of the [KernDX Strategic Guide](/strategic-guide-overview).

**Last verified:** 2026-11-17 (counts recomputed from the source tree for the 1.12 release, including 80 Jest test files and 3,597 Jest test cases, each test declaration counted once; package-version rows re-verified the same day against `sfdx-project.json` at 1.12.0-3)
**Source:** Counts derive from the `force-app/` source tree and from `git log` on the **Last verified** date above. Update this file when the codebase changes.

---

## Table of Contents

<details>
<summary>Expand</summary>

1. [Package Codebase](#package-codebase)
2. [Org Apex Usage (Unmanaged)](#org-apex-usage-unmanaged)
3. [Global API Surface](#global-api-surface)
4. [Extension Points (Where Your Code Connects)](#extension-points-where-your-code-connects)
5. [LWC Components](#lwc-components)
6. [Salesforce Metadata](#salesforce-metadata)
7. [Documentation](#documentation)
8. [Code Quality & Scanning](#code-quality-scanning)
9. [Release Testing](#release-testing)
10. [E2E Tests (Playwright)](#e2e-tests-playwright)
11. [Combined Test Coverage](#combined-test-coverage)
12. [Activity Snapshot](#activity-snapshot)
13. [The Other Frameworks We Compared](#the-other-frameworks-we-compared)

</details>

---

## Package Codebase

| Metric                          |                Count | Notes                                                                                                                                              |
|---------------------------------|---------------------:|----------------------------------------------------------------------------------------------------------------------------------------------------|
| Apex classes (total)            |                  410 | sum of production + test                                                                                                                           |
| Apex production classes         |                  204 | `force-app/main/default/classes/*.cls` excluding `_TEST.cls`                                                                                       |
| Apex test classes               |                  206 | `force-app/main/default/classes/*_TEST.cls`                                                                                                        |
| Apex test methods               |                6,380 | counted from `force-app/main/default/classes/*_TEST.cls` (method-level `@IsTest` annotations; class-level `@IsTest(...)` annotations are excluded) |
| Apex test coverage              |        100% per-file | enforced at every release build by `scripts/evaluate-coverage.js`                                                                                  |
| Lines of code (production Apex) |                ~105K | counted from `force-app/main/default/classes/*.cls` excluding `_TEST.cls`                                                                          |
| Lines of code (test Apex)       |                ~114K | counted from `force-app/main/default/classes/*_TEST.cls`                                                                                           |
| Lines of code (production LWC)  |                 ~27K | counted from `force-app/main/default/lwc/**/*.js` excluding `.test.js`                                                                             |
| Lines of code (LWC Jest tests)  |                 ~49K | counted from `force-app/main/default/lwc/**/*.test.js`                                                                                             |
| Lines of code (total)           |                ~294K | the rows above are rounded; exact total 294,036                                                                                                    |
| Source API version              |                 68.0 | visible in Setup → Installed Packages → Kern → API Version; also in `sfdx-project.json`                                                            |
| Latest packaged version         |        1.12.0-3 (released) | `sfdx-project.json` `packageAliases`                                                                                                               |

## Org Apex Usage (Unmanaged)

| Metric                 |      Value |
|------------------------|-----------:|
| Apex characters in use |  1,209,561 |
| Apex character limit   | 10,000,000 |
| Percent of limit used  |     12.10% |

> The org measured here is the development org, which is a scratch org, and Salesforce gives scratch orgs a 10 MB limit ([Apex governor limits](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm): "For scratch orgs, the limit is 10MB."). Against the standard 6 MB limit, the same code would use about 20%.
>
> You can see this figure yourself in Setup → System Overview. The count includes every Apex class and trigger defined in the org, excluding comments and test classes (those annotated `@IsTest`). Managed package code does not count towards this limit, which is why installing KernDX as a managed package leaves your org's own Apex headroom untouched.

## Global API Surface

| Metric                        | Count |
|-------------------------------|------:|
| Global classes (top-level)    |   109 |
| Global interfaces (top-level) |     4 |
| Global inner classes          |   ~94 |
| Global inner interfaces       |   ~26 |
| Global inner enums            |   ~16 |
| Global methods                |  ~556 |

## Extension Points (Where Your Code Connects)

> The points where your own code connects to the framework. The [Global API Surface](#global-api-surface) section above counts the raw symbols (classes, methods, and so on). This section is more useful day to day: it groups those connection points by *how* you use them, so you can tell at a glance whether a given extension needs configuration, Apex, or just clicks in Flow.

### Metadata-Configured (no code required)

| Metric                           | Records | Notes                                                                                                        |
|----------------------------------|--------:|--------------------------------------------------------------------------------------------------------------|
| `TriggerSetting__mdt`            |       7 |                                                                                                              |
| `TriggerAction__mdt`             |      11 |                                                                                                              |
| `FeatureFlag__mdt`               |      15 | excluding the `TestFeatureFlag` fixture record                                                               |
| `FeatureFlagStrategy__mdt`       |       6 | excluding the `TestFeatureFlagStrategy` fixture record                                                       |
| `ApiSetting__mdt`                |       4 |                                                                                                              |
| `ApiCredential__mdt`             |       3 |                                                                                                              |
| `MaskingRule__mdt`               |      18 | 3 active by default (MaskSecretKeys, MaskPaymentCard, MaskJwt), 15 shipped inactive (14 templates and the legacy MaskCreditCard that MaskPaymentCard replaces) |
| `MaskingTarget__mdt`             |      14 | Wildcards wiring the card and secret rules to ApiCall__c, ApiIssue__c, AsyncChainExecution__c, and LogEntryEvent__e, and the JWT rule to ApiCall__c and ApiIssue__c (ApiCall_All_Jwt, Issue_All_Jwt); 4 of the 14 belong to the replaced credit-card rule and ship inactive |
| `ApiMock__mdt`                   |       0 | Extensibility-only: no pre-built records, you add your own                                                  |
| `ValidationRuleGroup__mdt`       |       0 | Extensibility-only: no pre-built records, you add your own                                                  |
| `ValidationRule__mdt`            |       0 | Extensibility-only: no pre-built records, you add your own                                                  |
| `ClassTypeResolver__mdt`         |       0 | Extensibility-only: no pre-built records, you add your own                                                  |
| `AsynchronousJobSetting__mdt`    |       1 | `JobRunnerCheckLimit`, for the scheduled job runner; you add your own for other jobs                         |
| `FieldSetGroup__mdt`             |       0 | Extensibility-only: no pre-built records, you add your own                                                  |
| `PostTriggerAction__mdt`         |       0 | Extensibility-only: no pre-built records, you add your own                                                  |
| **Total pre-built custom metadata (CMDT) records** |  **79** | excluding the two `Test*` fixture records                                                                    |

### Code-Level (extend or implement)

| Metric                        | Count | Composition                                                                                                                                                    |
|-------------------------------|------:|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Base classes to extend        |     8 | `SEL_Base`, `TRG_Base`, `API_Outbound`, `API_Inbound`, `SCHED_Base`, `DTO_JsonBase`, `UTIL_TypeResolver.BaseClassResolver`, `TST_Builder.DefaultValueProvider` |
| Top-level interfaces          |     4 | `IF_Queryable`, `IF_Schedulable`, `IF_Search`, `IF_TableDataSource`                                                                                            |
| `IF_Trigger` inner interfaces |     7 | BeforeInsert, AfterInsert, BeforeUpdate, AfterUpdate, BeforeDelete, AfterDelete, AfterUndelete                                                                 |
| `IF_Async` inner interfaces   |     2 | Processable, Finishable                                                                                                                                        |
| Other inner interfaces        |     4 | `IF_Chain.Step`, `QRY_Condition.Evaluable`, `UTIL_TypeResolver.INT_ClassTypeResolver`, `SVC_Omnistudio.OmniCallable`                                           |
| ComponentBuilder LWC modules  |     6 | `notification`, `controller`, `navigation`, `lightning-message`, `flow-navigation`, `all`                                                                      |

### Declarative (Flow Builder / Lightning App Builder)

| Metric                            |                  Count |
|-----------------------------------|-----------------------:|
| Flow invocable actions (`FLOW_*`) |                     16 |
| Exposed LWC components            |                     33 |
| LWC with Lightning page targets   |                     15 |
| — App Page                        |                     11 |
| — Home Page                       |                      7 |
| — Record Page                     |                      6 |
| — Flow Screen                     |                      5 |
| — Tab                             |                      1 |
| — Record Action                   |                      1 |
| Pre-built flows                   |                      6 |
| Platform events                   | 1 (`LogEntryEvent__e`) |

## LWC Components

| Metric                 |                        Count | Notes                                                             |
|------------------------|-----------------------------:|-------------------------------------------------------------------|
| LWC components (total) |                           78 | `force-app/main/default/lwc/**/`                                  |
| Jest test files        |                           80 | counted from `force-app/main/default/lwc/**/*.test.js`            |
| Jest test cases        |                        3,597 | each test declaration counted once; a Jest run reports more, because it runs a table-driven test once per row |
| Jest test coverage     | 95%+ statement / 95%+ branch | enforced at every release build by `scripts/evaluate-coverage.js` |

## Salesforce Metadata

| Metric                          | Count |
|---------------------------------|------:|
| Custom objects (`__c`)          |    11 |
| Custom metadata types (`__mdt`) |    15 |
| Platform events (`__e`)         |     1 |
| Custom fields (total)           |   304 |
| — on custom objects             |   162 |
| — on custom metadata types      |   122 |
| — on platform events            |    20 |
| Pre-built CMDT records          |    79 |

## Documentation

| Metric                                        | Count | Notes                                                                                                                       |
|-----------------------------------------------|------:|-----------------------------------------------------------------------------------------------------------------------------|
| Developer guides                              |    21 | Excluding the Strategic Guide series; counted from `docs/*%20-%20Guide.md`                                                  |
| Fast Start guides                             |    17 |                                                                                                                             |
| Strategic Guide documents                     |     9 | Overview + Architecture & Philosophy + Adoption + Operations + Risks + Glossary + Personas + Metrics + Choosing a Framework |
| API reference pages (Apex)                    |   252 |                                                                                                                             |
| API reference pages (metadata)                |    16 |                                                                                                                             |
| API reference pages (objects)                 |    12 |                                                                                                                             |
| API reference pages (events)                  |     2 |                                                                                                                             |
| API reference pages (total)                   |   282 | sum of all reference categories                                                                                             |
| Total documentation files (developer-focused) |    47 | 21 developer guides + 17 Fast Start guides + 9 Strategic Guide documents (excluding `reference/`)                           |
| Security Guide (lines)                        | 2,511 | bespoke threat-model guide; counted from `docs/Security - Guide.md`                                                         |

> The headline figure quoted in companion docs is 38 developer documents (21 guides + 17 Fast Starts), matching the per-category totals above.

## Code Quality & Scanning

| Metric                       | Count |
|------------------------------|------:|
| PMD rules (KernDX custom)    |    28 |
| ESLint rules (KernDX custom) |     8 |
| Node validators              |     4 |
| Total scanner checks         |    40 |

## Release Testing

These tests run in a separate org with the package installed the way you would install it (the rows call it the subscriber org: the org a package is installed into). The end-to-end (E2E) browser tests are counted under E2E Tests (Playwright) below.

| Metric                                | Count |
|---------------------------------------|------:|
| Subscriber Apex classes (production)  |    88 |
| Subscriber test classes               |    66 |
| Subscriber test methods               |   388 |
| Anonymous Apex test sections          |    85 |
| Anonymous Apex assertions (`PASS:`)   |   463 |
| Anonymous Apex assertions (`Assert.`) |   595 |

### Local test run

The package's own Apex tests, run on a computer with no Salesforce org. The figures below are written by `scripts/aer-run.js` into `verify-results/aer-run.json`, and the docs check fails when this table and that file disagree.

| Metric                               | Value                                                                                                                                                |
|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
| Apex tests passing locally           | 6,370 of 6,380 (99.84%)                                                                                                                              |
| Runtime                              | [aer](https://github.com/octoberswimmer/aer-dist) 1.6.10 by October Swimmer, a local Apex runtime                                                    |
| How it ran                           | as a user with the Administrator permission set (`-p Administrator`), on a copy of the source with no `profiles` folder, in one run                  |
| Source                               | v1.12.0-3                                                                                                                                            |
| Measured                             | 2026-11-18                                                                                                                                           |
| Failing: aer differs from Salesforce | 10                                                                                                                                                   |
| Failing: cause not yet known         | 0                                                                                                                                                    |

> What the runtime cannot run: the two "Failing" rows above. aer copies most of how Salesforce behaves, not all of it, so a real org stays the final word. Each failing test is listed with its reason in `scripts/aer-baseline.json`. On this run 10 tests failed. Each one passes in a Salesforce org, and each one fails on aer because aer behaves differently from Salesforce:

| Where aer differs from Salesforce                                                                                                                                 | Test it affects                                                                                            |
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|
| aer counts the Apex type `System.Location` as a record object, so finding the Location object by name fails with a type error; Salesforce does not                 | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneChecksATypeofWhoseWhenNamesLocationLikeAnyObject`         |
| aer finds no event for a filter on the phone of the person the event is about (`Who.Phone`); Salesforce finds the event                                           | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneReadsANameRecordFieldThatTheRelatedObjectHides`           |
| aer finds no event for a filter on the last name of the person the event is about (`Who.LastName`); Salesforce finds the event                                    | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneReadsAPathThatCanPointToAnObjectTheUserCannotRead`        |
| aer looks for `What.ProfileId` on Account and the query fails; Salesforce reads it from Name, the shared object that stands for any record `What` can point to    | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneReadsTheUserFieldsOfTheNameRecordForAStandardUser`        |
| In user mode (the user's own permissions apply), aer runs a query that sorts on a parent field the user cannot read; Salesforce refuses it                        | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneRefusesAHiddenFieldOfAParentTheUserCanRead`               |
| In user mode, aer runs a query that selects a field through a lookup the user cannot read; Salesforce refuses it                                                  | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneRefusesAPathThroughALookupTheUserCannotRead`              |
| In user mode, aer runs a query that selects `What.Name` when the user cannot read `WhatId`; Salesforce refuses it                                                 | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneRefusesASelectedPathThroughALookupTheUserCannotRead`      |
| In user mode, aer runs a `TYPEOF` query that names an object the user cannot read; Salesforce refuses it                                                          | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneRefusesATypeofWithATypeTheUserCannotRead`                 |
| For a Minimum Access user, aer says `RecordTypeId` on Name can be read, so the query fails; Salesforce says it cannot, so KernDX refuses the query before it runs | `QRY_BuilderBypassSharing_TEST.bypassSharingAloneRefusesTheUserFieldsOfTheNameRecordForAMinimumAccessUser` |
| aer counts the Apex type `System.Location` as a record object, so finding the Location object by name fails with a type error; Salesforce does not                 | `UTIL_SObjectDescribe_TEST.shouldFindObjectWhoseNameIsAlsoSystemTypeName`                                  |

## E2E Tests (Playwright)

| Metric              | Count |
|---------------------|------:|
| Spec files          |    15 |
| Test cases          |   132 |
| Page objects        |    14 |
| Helper modules      |     8 |
| CMDT fixture states |    24 |

> The Test cases row counts the functional release-verification specs (parts 1 to 12). Three further spec files sit outside that count: two capture the documentation screenshots (15 cases between them) and one checks the Log Console's shipped screens against the agreed design (3 cases). The Spec files row counts all 15 files.

## Combined Test Coverage

| Layer                       |         Tests |  Assertions |
|-----------------------------|--------------:|------------:|
| Package Apex tests          | 6,380 methods |      ~7,729 |
| Package Jest tests          |   3,597 cases |      ~5,054 |
| Subscriber Apex tests       |   388 methods |        ~349 |
| Subscriber anonymous Apex   |   85 sections |         463 |
| Subscriber E2E (Playwright) |     132 cases |        ~342 |
| **Total**                   |    **10,582** | **~13,937** |

> The Tests column is recounted from source every release. The Assertions column carries forward from the 1.6 reconciliation and was not recounted this release, except the anonymous Apex row, which takes the `PASS:` count from the Release Testing table above.

## Activity Snapshot

These figures describe how well-supported and ready-to-install the package is, measured on 2026-11-17. They are kept separate from the capability counts on purpose: how long a project has been active should not be confused with how much it does, so neither number skews the other. Figures derive from `sfdx-project.json` `packageAliases`.

| Metric                             |                Value | Source                                                                                  |
|------------------------------------|---------------------:|-----------------------------------------------------------------------------------------|
| Published managed-package versions |                  151 | `sfdx-project.json` `packageAliases`: `04tfj000000EtB7AAK` through `04tfj000000lFlBAAU` |
| Latest packaged version            |        1.12.0-3 (released) | `sfdx-project.json` `packageAliases`                                                    |
| Primary contributors               |                    1 | single-maintainer project                                                               |

> KernDX is a single-maintainer project. Its readiness to install shows up in the 151 published managed-package versions, rather than in a long public commit history. So what this means for you: the package itself is well-exercised through repeated releases, even though it does not yet have the years-long open commit log of an older project.

## The Other Frameworks We Compared

When the guides rank or compare KernDX, they measure it against the same group of other Salesforce frameworks across the same capability areas, so every comparison is like-for-like. This page only points you to the detail rather than repeating it: the Adoption and Architecture guides walk through how each area is covered, and the Risks guide covers maintenance and the bus-factor question (what happens if the people who built it move on).

---

[Strategic Guide (Overview)](/strategic-guide-overview)
