What it may solve
Office views for DSH Agent Teams.
Imported third-party catalog description; not a Registry verification conclusion.Office views for DSH Agent Teams.
Author: zaimokuza-yoshiteru · Docs & Rendering · Catalog snapshot: 2026-09-19Canonical semantic path
Office views for DSH Agent Teams.
Imported third-party catalog description; not a Registry verification conclusion.zaimokuza-yoshiteru/dsh-agent-teams-office
— stars · 0 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 4/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 0 stars, 4 commits, 0 forks, and 0 watches; latest commit 2026-09-17.
Conclusion: Resolved npm release 0.1.0-beta.1, published 2026-09-16, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan found 3 characteristics that need attention: contains credential or token handling code, may execute dynamically constructed code, may access the network. This is a bounded automated observation, not a determination of malicious intent.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @zaimokuza/dsh-agent-teams-office@0.1.0-beta.1; SHA-256: b812f071f0047aa9ccb5fa8165bac7c728726049da1533ed507ac857f9a81155.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention @zaimokuza/dsh-agent-teams-office. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@zaimokuza/dsh-agent-teams-officeAnalyzed 0.1.0-beta.1github:zaimokuza-yoshiteru/dsh-agent-teams-officeExact version not resolved