DSH Plugin Registry
中文EN
Submit plugin
Plugins/dsh-config-form

dsh-config-form

Automated evidence available

One settings page for every plugin that opts in: declare fields, get a rendered form

Author: begonia599 · Tools & Capabilities · Catalog snapshot: 2026-09-19

Canonical semantic path

Interface & PersonalizationSettings & Configuration UISettings Navigation Organization

One primary path; alternate capabilities remain separate.
config.layered-resolutionplugin-runtime.settings-seamsecurity.access-controlsecurity.loopback-origin-enforcementsecurity.secret-handling

What it may solve

One settings page for every plugin that opts in: declare fields, get a rendered form

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

begonia599/dsh-config-form

— stars · 635 downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.

Analysis complete

Source structure

Conclusion: The source structure check completed without finding a structural issue.

Analysis complete

Repository health

Conclusion: The GitHub repository is reachable and not archived. Public data: 0 stars, 7 commits, 0 forks, and 0 watches; latest commit 2026-08-17.

Analysis complete

npm release

Conclusion: Resolved npm release 0.2.0, published 2026-08-17, license MIT.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis complete

Static risk scan

Conclusion: The scan observed 3 code capabilities: declares a prepare script, normally used when building or publishing the package, contains credential or token handling code, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.

Analysis complete

Package integrity

Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-config-form@0.2.0; SHA-256: 9b9b43905f58bc86d30f7b931a1e851c1a84a83281ca033b54cedbb8c573b50b.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-config-form. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.

Install or update the plugin manager (latest)