Pinned commit, README, license, and a declared package identity.
Transparent registry evidence
Evidence methodology
The Evidence Score measures how much reviewable information a repository publishes, and how far each statement can be traced. It is not a compatibility percentage, not a certification, and it awards no points for checks this registry has not run.
How the score is composed
An install command that can be traced to the README or package metadata.
Recent pushes, tagged releases, and an unarchived repository.
A stated DSH version outranks profile or platform claims alone, and official core packages belong in peerDependencies rather than private installs.
No install-time scripts, a detected license, no high-severity static findings.
Manifest-aware classification
The root package.json declares dsh.bundle and the patch file it points at exists in the tree. Both are required.
DSH-specific behaviour is present without a complete native bundle manifest.
The topic alone is never treated as proof that a repository is an installable plugin.
Compatibility confidence
An exact DSH version is documented.
Profile or platform claims exist without a stated version.
No reliable compatibility claim was found.
What this registry does not run
No package is installed, so no install result is claimed.
No plugin is executed and no behaviour is observed.
Published vulnerability advisories are not independently checked.
Static signals cannot prove a plugin is safe, future-compatible, or free of hidden behaviour. Review the source, pin a commit, and test in a disposable profile before trusting any record here.