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

@tutti-os/app-release-tools

v0.0.263

Published

Command-line tools for publishing Tutti workspace apps into App Center release metadata.

Vulnerabilities

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

Links

Git

Maintainers

hugozhou0638hugozhou0638jomeswangjomeswangvorshenvorshenrv4norv4nojacksooon.0113jacksooon.0113

Keywords

Readme

@tutti-os/app-release-tools

Command-line tools for publishing Tutti workspace apps into App Center release metadata.

Commands

build-tutti-app-release --app-id vibe-design --package-dir dist/tutti-app/vibe-design --base-url https://cdn.example.test/tutti-app-releases
build-tutti-app-versions --release-file ./apps/vibe-design/0.2.0/release.json --min-tutti-version 0.12.0 --output ./apps/vibe-design/versions.json
build-tutti-app-catalog --versions-file ./apps/vibe-design/versions.json --output ./catalog.json
build-tutti-app-catalog --existing-catalog ./catalog.json --versions-file ./apps/vibe-design/versions.json --output ./catalog.json
verify-tutti-app-release-artifacts --release-file ./apps/vibe-design/latest.json
verify-tutti-app-release-artifacts --catalog-file ./catalog.json --versions-file ./apps/vibe-design/versions.json

The release command validates a complete Tutti app package, creates a reproducible zip with stable entry ordering and timestamps, writes immutable release.json, and writes mutable latest.json. Rebuilding the same package version produces the same artifact SHA-256, so an interrupted release can safely verify and reuse its immutable upload. When the manifest declares localizationInfo, the release metadata includes the referenced manifest locale files so App Center can localize uninstalled remote apps without downloading the package.

App CLI manifests may declare execution.mode: "wait" for commands that block until a run or session reaches a stop point. Wait commands use JSON output and must leave --timeout-ms to the Tutti CLI as the optional total wait deadline; App input schemas must not redefine it.

The versions command maintains one mutable tutti.app.versions.v1 index per app. Every catalog-eligible release has an explicit minimum Tutti version and an active or withdrawn status. Reusing an immutable app version with changed release or compatibility metadata is rejected.

The catalog command merges version indexes into tutti.app.catalog.v1. apps[] contains the highest active app version whose minimum Tutti version is 0.0.0, so old Tutti clients remain safe. compatibility.apps contains only the compact compatibility frontier needed by new Tutti clients, not every historical release. Catalog output is rejected when it exceeds the legacy 1 MiB reader limit. The older --release-file form remains available for legacy tooling but does not create compatibility metadata.

The verify command checks release and catalog metadata against the referenced artifact downloads. When --catalog-file is combined with --release-file or --versions-file, catalog entries for those apps must exactly match the corresponding release metadata before artifact SHA-256 and size checks run.

publish-tutti-app-metadata and publish-tutti-app-catalog update mutable S3 JSON objects with ETag conditional writes and retry on concurrent changes. They bootstrap a missing versions index from the exact immutable release currently present in the legacy catalog; they never infer legacy compatibility from a newer latest.json object. Catalog publication validates all metadata and downloads referenced artifacts before attempting the conditional S3 write.