npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ch4acko3/dsh-agent-fleet-lark

v0.1.0

Published

Lark and Feishu connector for Agent Fleet Gateway

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ch4acko3ch4acko3

Keywords

Readme

Agent Fleet Lark

Lark and Feishu integration for Agent Fleet. It exposes two deliberately separate identities:

  • A bot connector backed by @larksuite/channel, registered with Fleet Gateway for long-running inbound and outbound messaging.
  • Identity-pinned lark-cli adapters at ctx.fleetLark.user and ctx.fleetLark.bot. Every business command is spawned directly with an explicit --as user or --as bot; Fleet never silently switches identity.

Set LARK_APP_ID and store the App Secret under the DSH credential reference LARK_APP_SECRET to activate the realtime bot connector. Both CLI identities use the existing lark-cli profile and remain idle until DSH calls them. LARK_CLI_PATH and LARK_CLI_PROFILE optionally select a binary and profile.

The package performs transport and identity adaptation only. Fleet Mailbox owns persistence and Team routing; DSH decides which identity and capability to expose.

Fleet registers lark.read, lark.message-post, lark.content-write, lark.manage, and lark.act-as-user plus the lark-resource resource kind. Trusted DSH adapters call ctx.fleetLark.executeForAgent(...) with an Agent id, classified action, and canonical resource. User-identity calls require both the business action and lark.act-as-user; raw CLI adapters remain Host-only.