dsh-fs-encoding

Automated evidence available

File encoding guard: byte-exact read/write/edit for GBK, Big5, Shift-JIS, EUC-KR, Windows-125x, UTF-16 and UTF-32 files, so editing a legacy file leaves it in its original encoding instead of silently rewriting it as UTF-8; UTF-8 BOM preserved exactly as it was, line endings (CRLF/LF/CR) kept, characters the encoding cannot represent refused rather than written as "?", and non-UTF-8 files listed with candidate encodings so the model can re-read them explicitly.

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

Canonical semantic path

Files, Documents & KnowledgeWorkspace File Browsing & Editing

One primary path; alternate capabilities remain separate.

What it may solve

File encoding guard: byte-exact read/write/edit for GBK, Big5, Shift-JIS, EUC-KR, Windows-125x, UTF-16 and UTF-32 files, so editing a legacy file leaves it in its original encoding instead of silently rewriting it as UTF-8; UTF-8 BOM preserved exactly as it was, line endings (CRLF/LF/CR) kept, characters the encoding cannot represent refused rather than written as "?", and non-UTF-8 files listed with candidate encodings so the model can re-read them explicitly.

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

Sources and public signals

MrWeiCodes/dsh-fs-encoding

3 stars · 166 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 1/5. Historical chains are retained but do not count toward current coverage.

Not analyzed

Source structure

Source structure has not been analyzed.

Not analyzed

Repository health

Repository metadata has not been analyzed.

Not analyzed

npm release

npm release metadata has not been analyzed.

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, may read environment variables, may create or modify files. 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-fs-encoding@1.3.0; SHA-256: 35452390d74de183646290ff1ce6b7843233ce97b7ea434258de6c198134ca97.

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-fs-encoding. 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)