How to Read DSH Hunt Static Evidence

A practical guide to source revisions, static findings, coverage states, limits, and correcting a DSH Hunt report.

A DSH Hunt report is a record of specific observations, tied to a source revision and an analysis method. Read the source, coverage, result label, and limits together. A finding is evidence to inspect, not a verdict about a project.

Start with the evidence sources

The current plugin profile reads a package Manifest, an approved cordis.patch.yml, and at most one supported root README up to 64 KiB. Each finding links to a source path and locator when one is available. Tree observations can record whether selected license or shell paths exist without reading their contents. Use the page's coverage section to see which of these inputs were captured for that report.

GitHub repository metadata is a timestamped observation. Exact-version npm Registry metadata is collected only for some reports and, when present, is separately timestamped; the DSH Notify example below did not query the Registry. Registry identity fields do not verify tarball bytes or prove that a package came from the linked commit. Follow each source link; do not treat the page as one undifferentiated result.

Keep the report attached to its exact revision

A full commit SHA identifies the repository revision named by the report. Open the commit, then open the Manifest or Patch at that same revision. A branch or tag can move later; the SHA makes it possible to revisit what the report actually observed.

A newer commit is a different source snapshot; it does not change what the older report observed. A commit also does not prove that a Registry tarball was built from that source. The npm gitHead field is a publisher-provided claim, not reproducible build proof.

Read states as limits on what is known

A state describes the collection outcome for a field or file. It is not interchangeable with a negative finding.

Observed / read
The report captured the named file or field at the pinned commit. This does not describe files or behavior outside that scope.
Unobserved / not read
The item was outside the collected evidence. It does not prove the repository has no such file, declaration, or behavior.
Pending / not captured
Collection did not complete or the observation was not retained. Check the reason and source fields; do not treat it as absence.
Unknown
The record cannot establish a value, such as a classification or freshness state. Unknown is distinct from observed absence and from a failed check.

See the evidence status definitions for the full publication and collection states.

Treat findings as scoped observations

A finding is emitted when a rule matches data inside the profile's captured inputs. Its evidence path and locator let you compare the explanation with the source. Read the rule name, explanation, recommendation, and the statement about what the result does not establish; the finding count is not a risk score or a ranking.

At commit 8f386ca5d66e8549119466c4a2ede15154aad577, the DSH Notify report has three informational findings: two record peer ranges whose runtime compatibility was not tested; one notes a missing homepage declaration. They describe Manifest facts and rule limits, not whether the plugin works or is safe.

Understand what static evidence cannot establish

DSH Hunt does not execute plugin code, installers, lifecycle scripts, or build commands. A manifest declaration is not runtime behavior. Static evidence cannot establish successful installation, compatibility, or whether code is benign or malicious.

Coverage narrows conclusions. If entry source, README, license text, shell source, or runtime was not read or tested, check the report's coverage. No findings means no covered rule matched the captured inputs; it is not a clean bill of health.

A report's inclusion or publication in DSH Hunt is not a recommendation, security certification, or compatibility approval.

Read the collection methodology for the profile's current scope.

Check declarations without turning them into endorsements

Keep the GitHub repository license marker separate from the package Manifest license. The marker is observed at a collection time; the package value is declared in a fixed file. Neither is a legal review. Read unknown reasons and source links; do not infer one value from the other.

Fields such as dshEngine, nodeEngine, and peerDependencies are Manifest declarations. Compare them with your environment, but do not treat matching ranges as compatibility tests. The analyzer version and profile describe the rules and inputs used.

A real plugin report to inspect

The DSH Notify page shows the fixed commit, source file links, three informational findings, analyzer version, and a partial-coverage notice. Open it to compare the report labels with the evidence and the areas it says were not checked.

DSH Notify

Plugin static analysis
Published plugin report
dsh-browser-notify-plugin
Repository
classfieldseason-cmd/dsh-notify-plugin
Analysis profile
manifest-patch-v1
Analyzer versions
Ruleset static-v1; source analyzer 0.2.0
Findings
3 findings; 3 informational; partial coverage
Manifest
package.json

This example uses its recorded manifest-patch-v1 profile. Its README was not read. Check this report's coverage when comparing it with the current profile.

Package-level structure is a separate report

This approved ReMe package report records structure and manifest fields at its own fixed commit. It does not contain a plugin static-analysis result, which is why package-level observations and plugin findings should not be described as the same report type.

ReMe

Package structure
Package-level report
@agentscope-ai/reme-dsh-plugin
Package ID
680d388e1a913555b194e6816c35a8702c249527072ffbf1d9093b950e5f2d27

Question or correct a report with primary evidence

For a factual field correction, identify the page and field, copy the value currently shown, state the proposed value, and link the public primary source at the relevant revision. The evidence-correction form includes the report identity and fixed commit when the page can supply them. Link to a source file rather than pasting private code or large copyrighted text.

Use a false-positive appeal for a specific classification or rule result, and methodology feedback for a proposed method change. Each GitHub Issue is public. Do not include credentials, private code, personal information, or sensitive vulnerability details. No response time is promised.

Open the example package report's correction formOpens a public GitHub Issue form; visiting it does not submit a request.

A review can be accepted before the site changes. Acceptance means the evidence was reviewed for the proposed update; it is not publication, a security endorsement, or runtime approval. The published status belongs only after a release is live and the affected page has been checked. Read the methodology and status definitions alongside any report.