Evidence stays attached to its source.
Every report names a fixed source revision. Its recorded scope and version information let you revisit what was observed, how it was collected, and what remains unknown.
Community directory reports analyze pinned directory metadata. Only pages labeled as fixed-source reports record inspection of the target repository's code.
Read the guide to static evidence- Pin the source
An exact commit and its file paths.
- Record the scope
The inputs captured and the method used.
- Read the evidence
Observations with their limits attached.
Fixed revisions
DSH Hunt does not treat a floating branch HEAD as permanent evidence. A repository may change after analysis; the record continues to name the exact 40-character commit that was observed.
Version information describes the method behind that observation. The fields depend on the report type:
- Static analysis
- Analyzer version and analysis profile
- Structure reports
- Collector, policy, and schema versions
What the analyzer reads
The current static-analysis profile uses a defined set of inputs. Source paths and locators stay attached to each declaration-level finding.
| Input | Scope and recorded evidence |
|---|---|
| Package Manifest | Declared metadata, with source paths and locators for the findings it supports. |
| Approved Patch | cordis.patch.yml. Syntax outside the supported profile is held, not silently treated as valid. |
| Root README | At most one supported file, up to 64 KiB. The analyzer scans installation and configuration headings, then stores only its path, Git Blob SHA, byte size, and those two heading-presence facts. |
| Selected file paths | Tree metadata records whether selected license and shell paths exist. Their contents are not read. |
Execution is outside this profile
DSH Hunt does not execute third-party plugin code, lifecycle scripts, installers, or build commands.
This static-analysis profile does not query npm Registry. Exact-version Registry metadata, when collected, is stored as a separate timestamped observation. It does not verify package artifact bytes or provenance.
How to read the output
- Capability signals
- Describe observed surfaces, not a risk score.
- Static analysis labels
- Count signals covered by the current rules. They are not safety or quality ratings; no covered findings does not establish that a package is safe.
- Structural validity
- Does not establish runtime compatibility. Static analysis is not a security audit.
- Repository metadata
- GitHub repository metadata is labeled with its observation time. Read it separately from evidence pinned to a source commit.
Unknown is not a negative result
Unknown limits what the report establishes; it does not mean absent or safe. Read the field’s reason: “not read,” “not captured,” and observed absence describe different states. Unknown also differs from a failed check.
One report, distinct license sources
The approved Petdex report pins its package source to this commit:
a1b229116968cbe9f3a9b2141634a9baa0819864- Package Manifest
- No
licensefield declared - LICENSE at the same SHA
- MIT in the separate license file
- Repository license marker
- MIT recorded at repository level
These sources are distinct. Neither the license file nor the repository marker supplies a package Manifest declaration.
Open the Petdex reportVerify the full SHA, path, and Blob SHA; read coverage and the status reason. If source and page conflict, use the correction link with current and proposed values and a primary source. The status model and guide explain limits. This is not a legal, runtime, or safety assessment.
Corrections and appeals
A correction stays tied to the evidence it changes. Acceptance and publication are separate steps.
Identify the field and source
Use the correction link on the affected evidence page. Include the field, its current value, the proposed value, and a public primary source supporting the change.
Review at the pinned revision
An accepted metadata correction is bound to that exact report and source commit. The original observation and review reason remain traceable.
Publish through a reviewed release
Acceptance starts a release review; it does not mean the site has changed. A correction is published only after a release is live and the page has been checked.
A false-positive appeal about a rule must identify the report’s pinned commit. A newer commit is a separate source revision and does not erase what the older report observed. A reproducible rule defect receives a narrow regression case before the rule changes; that change applies through a reviewed report release.
Choose a public reporting route
Every GitHub Issue is public. Do not include secrets, private source code, or sensitive vulnerability details.
- Correct an evidence fieldA factual value and the public source supporting it.
- Appeal a false-positive classificationA rule result at the report’s pinned commit.
- Give methodology feedbackA proposal about collection, analysis, or interpretation.
- Ask about a private reporting routeA public question only. Include no details about the concern.
No private security reporting route has been verified. The route-question Issue remains public and does not privately deliver a vulnerability report.
