Toolmark Check a package

Methodology and rules

These rules hold for every report. If one of them ever has to change, the change and its date are written here.

No score

There is no score, grade, rating or badge. A report lists what we observed, with the evidence, the source and the date.

Three labels

Every finding is verified (we saw it hold), a review item (something worth a human look) or not tested. Claims a tool makes about itself stay claims until we observe them.

Not tested is never held against a tool

If we could not test something, for example because it acts outside the box or needs a real account, it is labelled not tested. It never lowers anything, because nothing is being added up.

Hint checks are review items

When a tool says "read-only" and changed files in our data folder, that is a review item, not a failure. Some reads legitimately rewrite metadata. We only turn a pattern into a failure after measurement rounds show it is reliable.

What counts as a failure

Only what a tool contradicts in its own declarations, for example output that breaks its own declared schema, or answers that break the protocol.

We never describe a tool as free of risk

Toolmark is not a vulnerability scanner and does not say a tool meets any standard. On standards and regulations we only repeat what the provider claims, labelled as their claim.

Payment never changes a result

Nothing is for sale today. If paid features ever exist, payment will not change what a report says, how it is ordered or who is told about it.

One version, one day

A report is about the exact version that ran on the date shown. It says nothing about other versions or about the provider's hosted service.

What we never do

  • No sign-in bypass, account creation, CAPTCHA solving or password guessing.
  • No outward call that could reach anyone: outward tools run only with the network proven closed and fake values.
  • Servers we do not own get only the two protocol requests that read the tool list.
  • Third-party code never runs on our own machines.
  • No real personal data in any test.

Corrections

If you think a finding is wrong, write to contact@toolmark.dev with the report link. We rerun the check and correct the method if the error is ours.

One package at an exact version, a private link to the report.

Check a package