Sealmark
Automated re-test on 2026-11-22: not checked by hand, and not yet reviewed by the maintainers.

Results / skilltotal

skilltotal

version tested 1.9.0PyPItested 2026-11-22Sealmark 1.0.1methodology 0.3-draftSTANDARD run3 tools

Sealmark's automated test of skilltotal 1.9.0 on 2026-11-22 gave it grade D, its lowest test-area grade (protocol D and effects A). Tools reached with a valid call: 2 of 3. Of its 6 checks, 4 passed, 1 failed and 1 partial. 3 more checks are advisory, and advisory checks never change a grade: 1 failed and 2 not applicable. The run used Sealmark 1.0.1 with the standard settings. The grade includes a finding under private disclosure; it still counts in full.

D

Grade D

The server's grade is its lowest test-area grade. How grading works

The grade includes a finding under private disclosure. It still counts in full.

Tools reached with a valid call: 2 of 3.

Grade by test area

D
Protocol2.5/4 points · capped at Dcritical: tool-poisoningincludes a finding under private disclosure
A
Effects2/2 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 3 well-formed tool(s)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
fail
A security finding is being reported to the maintainer privately. Details will be published when it is fixed or 90 days after the report (disclosure policy).
robust-input
Survives malformed tool input
partial
0 internals leak(s), 1 invalid call(s) accepted
secret-echocritical
No environment secret echoed in responses
pass
Details held back while a security finding in this test area is reported privately.
instructions-hygiene (advisory)
Server instructions name only tools that exist
fail
the server instructions names 1 tool(s) the server does not offer (threat_class)
refusal-quality (advisory)
Refusals say what to do next
n/a
no refusal was recorded in this run, so there is nothing to judge

Effects checks

CheckVerdictWhat happened
annotation-honestycritical
Read-only tools change nothing
pass
scan_component, list_rules declared read-only and changed nothing in the observed directories during a benign call
openworld-honesty
Closed-world tools stay on the machine
pass
1 closed-world tool(s) called; nothing connected to the loopback listener (path and git tools cannot be pointed at it, so this confirms only that nothing connected out during the call)
undeclared-writes (advisory)
Unannotated tools leave the sandbox unchanged
n/a
every tool carries annotations, nothing to check

Each check id links to what it tests and how to fix a failure. The same text is in sealmark explain <id>.

What was not covered

Grade over time

Since the run on

  • Server version changed from 1.8.0 to 1.9.0.

Unchanged: the same grade in every test area, the same Sealmark version (1.0.1).

  1. Dv1.1.0Sealmark 1.0.1
  2. Dv1.2.0Sealmark 1.0.1
  3. Dv1.3.0Sealmark 1.0.1
  4. Dv1.5.0Sealmark 1.0.1
  5. Dv1.8.0Sealmark 1.0.1
  6. Dv1.9.0Sealmark 1.0.1

Badge for the README

The badge shows this automated result for version 1.9.0. It is a link to this page, not a certificate, and it changes when the next re-test does.

Sealmark badge for skilltotal
The flat badge, one letter per graded test area.
[![Sealmark](https://sealmark.dev/badge/skilltotal.svg)](https://sealmark.dev/results/skilltotal/)

Files: badge SVG, card SVG, shields endpoint JSON.

Package facts

License
Apache-2.0

From PyPI, checked 22 Nov 2026. Plain facts about the package; they play no part in the grade.

Run it yourself

The command for this run is withheld while a security finding is reported privately. It is published with the report, when the finding is fixed or 90 days after the report.

Grade alerts

One email when the grade of skilltotal changes after a re-test. Nothing else, and every email has a link to stop them.

Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.

Is this wrong?

Reply to our private report or email disclosure@sealmark.dev and we will recheck it. Maintainers can ask for their server to be removed.

If we were wrong, we correct the page and add your reply. Security findings go to the maintainer privately first; see the disclosure policy.