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

@lijuneleven/iris

v0.2.131

Published

Feishu-first personal AI assistant powered by local Agents.

Readme

Iris

Install:

npm install -g @lijuneleven/iris
iris

The CLI starts the local Iris service. Pass server flags directly:

iris --port 9090
iris --config-dir /data/iris

One Iris service manages multiple Feishu bots. Use iris status, iris stop, and iris restart to inspect, stop, or restart the service. Port selectors and all are no longer accepted. Auto-start is enabled by default and can be disabled under Global Settings → Security.

Port 8080 keeps its configuration and runtime data in ~/.iris. Other explicitly selected ports are isolated automatically under ~/.iris/instances/<port>/, including configuration, database, uploads, session recovery data, and logs. --config-dir only overrides the configuration directory, while IRIS_HOME changes the instance root.

After the service is ready, Iris opens the local configuration page automatically. First launch uses a dedicated password-setup page with password confirmation; later visits use a dedicated login page, with a secure browser session retained for thirty days.

The installer downloads the platform binary from GitHub Release first, then falls back to Gitee Release. It also installs the Codex notify and Claude Code Stop completion hooks together with the Iris Feishu-context Skill for both Agents, and forces Codex check_for_update_on_startup = false without replacing other user settings. The CLI retries Agent integration setup on every service start, and iris --install-agent-hooks can run it manually. When a question lacks enough conversation context, that Skill requires the Agent to read the current group's latest messages before asking the user to repeat information.

The settings page includes an optional one-time environment check for Node.js, the headless browser, writable data storage, Feishu connectivity, and the configured Agent. The result is not saved and does not block setup.

On first launch Iris automatically chooses an installed Agent in this order: Codex, then Claude Code. Scanned built-in Agents use fixed commands, while the list supports multiple editable custom Agents; developer-mode Feishu cards use the same list. Restarts resume the exact recorded Codex, Claude Code, or aiden x codex session when its session ID is available.

Developer-only assistant mode is off by default. When enabled for a group session, mentioning the configured developer triggers the Agent and the final Feishu card identifies itself as that developer's assistant.