EXTREMELY agency
NPM · @EXTREMELY-AGENCY/MCP
Your agency of AI agents in your AI app: what agents did, approvals, requests, jobs and reports.
Available components
Last scanned (23 hours ago)
Scores higher than 59% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to maxkxd/extremely-autonomous-agents). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5005 tokens (~161/item across 31 items; 31 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +20
- Malware scan: unverified → pass ▲ security
- Source repository: unverified → pass ▲ security
- 5 Nov 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@extremely-agency/mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | maxkxd/extremely-autonomous-agents |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/maxkxd/extremely-autonomous-agents/.github/workflows/agency-mcp.yml@refs/heads/main |
| Rekor log index | 3693927261 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f5b28bc8cfb7268bbd4e7abcb4fe39a1ad739686e5f0db395b7294e5a99fba42116e110c6871173b9ae29bb696ae5a3946fada97daca665ce105f9318 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agency_today What the agency did today ~122
What the whole agency did since a time (default: the start of today, the agency's own clock): per agent its runs, output actions and last summary, plus what's waiting on a person (approvals, open requests).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| since | string | – | Optional: an ISO date or time, e.g. 2026-11-05 or 2026-11-05T09:00 |
No output schema declared.
No examples provided.
agent_activity What an agent did ~132
What one agent did since a time (default: the start of today): its DM channel posts (each run's write-up and the tools it used), the people's messages to it, and the jobs given to it.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id (list_agents) |
| limit | number | – | Optional: at most this many posts, newest kept (default 30) |
| since | string | – | Optional: an ISO date or time |
No output schema declared.
No examples provided.
answer_request Close a request ~105
Close a request: done (say what was done, so the agent knows) or rejected (anything drafted for it is discarded). The agent hears on its next run.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| answer | string | – | What was done, or why not |
| request_id | number | yes | The request number |
| status | string | yes | – |
No output schema declared.
No examples provided.
builder_guide Agent builder guide ~113
Read this first when making an agent: the agent builder's whole brief - how agents work here, the tool catalogue and default tiers, the tools every agent gets, this organization and the person, the fleet, connected services and their tools and events, the connected models, how to interview the person, and how to tier. create_agent's fields carry the rest.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
No output schema declared.
No examples provided.
check_build Check an agent build ~993
Check a build before creating it, without creating anything: the same input as create_agent. Answers with what's wrong, or what it would make.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| approval_hours | array | yes | One entry per T2 tool |
| charter | string | yes | The full CHARTER.md in Markdown, written for this organization: # CHARTER - <name>, then ## Mission, ## What this agent does, ## What this agent does not do, ## Autonomy tier (which actions are T0, T… |
| department | string | yes | – |
| events | array | yes | What wakes this agent besides its schedule: things happening at a service that it reacts to - a new error report, a support ticket, an alarm, a payment failing. Empty for an agent that only works on… |
| ferocity | object | yes | How hard it works at each ferocity level, set for this job. The person picks the level on the card. |
| kpi | array | yes | 1-4 actions whose successful calls are the real output of this agent. Never reads or plumbing. |
| max_runs_per_day | number | yes | Runaway backstop, not the cadence: comfortably above what the job needs |
| models | array | yes | Up to three models in order of preference, from "Models connected" only: the first is used, the others take over if it fails. Pick the best fit for the job - strong models for open-ended judgement, f… |
| name | string | yes | Short agent name, 1-3 words, title case, e.g. "Invoice Chaser" |
| natural_limits | array | yes | Caps on an action at every ferocity - ONLY ones the person asked for in this conversation, in their own words ("at most one post a day"). Never add one because it seems sensible: the agency is here f… |
| new_events | array | yes | Events nothing connected provides yet that this agent should wake on. The Agency Engineer sets each up and the person connects it. Empty when none. |
| new_tools | array | yes | Tools that neither the fleet nor the catalogue has and this agent needs. Empty when existing tools cover it. |
| person_notes | array | yes | New facts about the person you're talking to. Only what will still be true and useful to an agent months from now: lasting roles, responsibilities, preferences, standards and how they like to work. N… |
| profile_notes | array | yes | New facts about the organization that every agent should know. Only what will still be true and useful to an agent months from now: lasting roles, responsibilities, preferences, standards and how the… |
| report_place | string | – | Where this agent's reports go when the person named a place in this conversation: exactly where (a folder's full path, "email to the owner", the Drive folder or Notion page), then " | " and the tool… |
| tools | array | yes | Every tool the job needs. Leave out anything it does not need. Do not list the fleet plumbing. |
No output schema declared.
No examples provided.
create_agent Create an agent ~1,055
Add a new agent, as the app's agent builder would (read builder_guide first, and talk to the person the way it says): the full build - name, department, Charter, tools with tiers, events, KPIs, models, ferocity plan. Every id must exist (the guide lists them) or be one of its own new_tools / new_events, which go to the Agency Engineer as requests. Answers with what it made.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| approval_hours | array | yes | One entry per T2 tool |
| charter | string | yes | The full CHARTER.md in Markdown, written for this organization: # CHARTER - <name>, then ## Mission, ## What this agent does, ## What this agent does not do, ## Autonomy tier (which actions are T0, T… |
| department | string | yes | – |
| events | array | yes | What wakes this agent besides its schedule: things happening at a service that it reacts to - a new error report, a support ticket, an alarm, a payment failing. Empty for an agent that only works on… |
| ferocity | object | yes | How hard it works at each ferocity level, set for this job. The person picks the level on the card. |
| kpi | array | yes | 1-4 actions whose successful calls are the real output of this agent. Never reads or plumbing. |
| max_runs_per_day | number | yes | Runaway backstop, not the cadence: comfortably above what the job needs |
| models | array | yes | Up to three models in order of preference, from "Models connected" only: the first is used, the others take over if it fails. Pick the best fit for the job - strong models for open-ended judgement, f… |
| name | string | yes | Short agent name, 1-3 words, title case, e.g. "Invoice Chaser" |
| natural_limits | array | yes | Caps on an action at every ferocity - ONLY ones the person asked for in this conversation, in their own words ("at most one post a day"). Never add one because it seems sensible: the agency is here f… |
| new_events | array | yes | Events nothing connected provides yet that this agent should wake on. The Agency Engineer sets each up and the person connects it. Empty when none. |
| new_tools | array | yes | Tools that neither the fleet nor the catalogue has and this agent needs. Empty when existing tools cover it. |
| person_notes | array | yes | New facts about the person you're talking to. Only what will still be true and useful to an agent months from now: lasting roles, responsibilities, preferences, standards and how they like to work. N… |
| profile_notes | array | yes | New facts about the organization that every agent should know. Only what will still be true and useful to an agent months from now: lasting roles, responsibilities, preferences, standards and how the… |
| report_place | string | – | Where this agent's reports go when the person named a place in this conversation: exactly where (a folder's full path, "email to the owner", the Drive folder or Notion page), then " | " and the tool… |
| tools | array | yes | Every tool the job needs. Leave out anything it does not need. Do not list the fleet plumbing. |
No output schema declared.
No examples provided.
decide_approval Approve or reject an action ~123
Approve or reject one of the actions in list_approvals, as on the Approvals screen: approved, it runs now and the agent hears the result; rejected, the agent is told (with the note, if any).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| approval_id | string | yes | The id from list_approvals |
| decision | string | yes | – |
| note | string | – | Optional: why, for the agent |
No output schema declared.
No examples provided.
delete_agent Delete an agent ~89
Delete an agent: its files go, its approvals and requests are closed, work handed to it is closed as not done. Its past runs stay in Usage. Built-in agents can't be deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
No output schema declared.
No examples provided.
discard_integration Discard or remove an integration ~99
Throw away a draft (a redraft of a live one goes back to the live version), or remove an added integration entirely. Shipped ones can't be removed.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| integration_id | string | yes | The integration id |
| remove_live | boolean | – | Remove it even though it is live |
No output schema declared.
No examples provided.
give_events Subscribe an agent to events ~91
Subscribe an agent to live events: it wakes when they happen, as well as on its schedule. list_integrations shows each integration's events.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
| events | array | yes | Event ids (server.event) |
No output schema declared.
No examples provided.
give_task Give an agent a job ~116
Give an agent a job, from you: it starts on it as soon as it can and marks it done with the result (agent_activity shows it). For a question or a quick word, run_agent with a message instead.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id (list_agents) |
| task | string | yes | The whole job, with everything it needs to know |
No output schema declared.
No examples provided.
give_tools Give an agent tools ~80
Give an agent tools that a live integration (or the agency's built-ins) provides, each at a tier.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
| tools | array | yes | – |
No output schema declared.
No examples provided.
latest_report An agent's latest report ~89
An agent's latest report: the write-up of its last run that made one, and where its reports go (the place its person chose, e.g. a Drive folder).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id (list_agents) |
No output schema declared.
No examples provided.
list_agencies List your agencies ~42
Your own agency and every organization you are in, with your role in each and whether it answers right now. Pass one as `agency` to any other tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agents List agents ~73
Every agent: id, name, department, owner, state (active / draining = standby / stopped), ferocity level, models, and whether it is built in.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
No output schema declared.
No examples provided.
list_approvals List approvals ~77
Agents' actions waiting on a person in the app (sending, posting, going live...): only the ones that are yours to decide. decide_approval approves or rejects one.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
No output schema declared.
No examples provided.
list_integrations List integrations ~69
Every integration (the services agents' tools run on): connected or not, draft or live, its tools. Plus whether code plugins are allowed.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
No output schema declared.
No examples provided.
list_models List AI models ~57
The AI models connected in the app, which agents can be given (set_agent_models).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
No output schema declared.
No examples provided.
list_requests List requests ~83
Requests agents filed for things they can't do themselves: what they need, why, where each stands, and the conversation with the Agency Engineer.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| include_closed | boolean | – | Closed ones too (default: open only) |
No output schema declared.
No examples provided.
publish_integration Publish an integration ~159
Make a draft live, and optionally give its tools to an agent. A plugin first gets the independent security review; a serious finding stops it. Done here, it doesn't wait for the app's Approvals.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| events | array | – | For for_agent: its events the agent should wake on |
| for_agent | string | – | Optional: the agent that gets its tools |
| integration_id | string | yes | The draft |
| tools | array | – | For for_agent: the tools to give and their tiers (T0 read, T1 reversible write, T2 needs a person) |
No output schema declared.
No examples provided.
read_agent Read an agent ~80
An agent's files (CHARTER.md, TOOLS.yaml, KPI.yaml), its models and state, its last runs and its memory notes.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
No output schema declared.
No examples provided.
read_integration Read an integration ~85
An integration's definition (YAML), and a plugin's code. The shipped ones - brave-search (HTTP), github and gmail (code) - show the format.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| integration_id | string | yes | The integration id |
No output schema declared.
No examples provided.
reply_to_request Reply on a request ~93
Write in an open request, to the Agency Engineer (as in the app: everyone on the request sees it, and the Engineer is woken to answer).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| request_id | number | yes | The request number |
| text | string | yes | What to say |
No output schema declared.
No examples provided.
run_agent Run or message an agent ~99
Start an agent now. With a message, it answers it in its DM channel (as if the person wrote it); without, it does its job as on Run now.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
| message | string | – | Optional: what to say to it |
No output schema declared.
No examples provided.
set_agent Set an agent's ferocity or state ~114
An agent's ferocity (how hard it works: Chill, Steady, Driven, Relentless, Apocalyptic) or state (active, draining = standby: starts nothing itself, stopped: runs nothing). Built-in agents have neither.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
| ferocity | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
set_agent_models Set an agent's models ~100
An agent's models: up to three, in order of preference; it falls to the next when one fails. Each {connection, model, effort: low|medium|high|max}, from list_models.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
| models | array | yes | – |
No output schema declared.
No examples provided.
test_event Try an event ~95
Try an integration's event (draft or live) without waking anyone: a real poll showing what it finds, and the webhook address to paste into the service.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| event_id | string | yes | The event (server.event) |
| integration_id | string | yes | The integration id |
No output schema declared.
No examples provided.
test_integration Try an integration tool ~105
Call one of an integration's tools for real (a draft or a live one), and see what an agent would. A plugin's code can't be tried before it's published.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| args | object | – | Its input |
| integration_id | string | yes | The integration id |
| tool | string | yes | The tool id |
No output schema declared.
No examples provided.
write_agent_file Replace an agent's file ~120
Replace one of an agent's files: CHARTER.md (its job), TOOLS.yaml (tools, tiers, approval windows, ferocity plan) or KPI.yaml (which actions count as output). read_agent first. Its next run uses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| agent_id | string | yes | The agent id |
| content | string | yes | The whole new file |
| file | string | yes | – |
No output schema declared.
No examples provided.
write_integration Write an integration draft ~122
Save an integration definition (YAML, kind http | mcp | code) as a draft: it shows in the app's Settings > Connectors to be connected, and no agent can call it until publish_integration. Redrafting a live one keeps the live one working meanwhile. Keys and sign-ins are added by the person in Settings, never here.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| yaml | string | yes | The whole definition |
No output schema declared.
No examples provided.
write_plugin Write a code plugin ~135
Save a code plugin's TypeScript (only if code plugins are allowed in Settings): export default { tools: [{ id, tier, description, input, run: async (args, token, kit) => string }] }. Network only through kit.fetch; it runs sandboxed with the permissions its kind: code definition declares. It runs only once published.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Which agency: an organization you are in, by name or id (list_agencies). Leave out for your own agency. |
| code | string | yes | The whole TypeScript file |
| module | string | yes | The module name its definition names |
No output schema declared.
No examples provided.
How do I install the EXTREMELY agency MCP server?
EXTREMELY agency runs locally as an npm package, launched with npx -y @extremely-agency/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @extremely-agency/mcp
claude mcp add agency-extremely-agency -- npx -y @extremely-agency/mcp
What is the EXTREMELY agency MCP server?
EXTREMELY agency is an MCP server listed in the public MCP registry as agency.extremely/agency. Your agency of AI agents in your AI app: what agents did, approvals, requests, jobs and reports. This page covers its npm package (@extremely-agency/mcp).
Is the EXTREMELY agency MCP server safe to use?
EXTREMELY agency scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EXTREMELY agency MCP server expose?
EXTREMELY agency exposes 31 tools: list_agencies, list_requests, answer_request, reply_to_request, give_task, and 26 more. Their descriptions and schemas cost roughly 4,915 tokens of context every time the server is loaded.
Is the EXTREMELY agency MCP server still maintained?
EXTREMELY agency is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the EXTREMELY agency MCP server under?
EXTREMELY agency declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the EXTREMELY agency MCP server?
VerifyMCP ran 15 checks on EXTREMELY agency, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about EXTREMELY agency: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.