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

@putdotio/taizn

v2.2.3

Published

A typed Tizen TV packaging, install, remote-control, and live proof harness.

Downloads

1,198

Readme

Install

pnpm add -D @putdotio/taizn

Node >=24.19

Install the Tizen command-line tools separately and make sure tizen and sdb work locally.

Quick Start

Create taizn.json in the app directory, keep .taizn/ ignored, then run:

pnpm exec taizn check
pnpm exec taizn package
pnpm exec taizn install
pnpm exec taizn run

Common project files:

| Path | Purpose | | ---------------------- | ---------------------------------------------- | | taizn.json | App build, widget, signing, and variant config | | .taizn/.env | Optional local secrets read by Node | | .taizn/certificates/ | Optional local author and distributor certs | | .taizn/remote.json | Optional paired Samsung TV remote token | | .taizn/seller.json | Local Seller Office browser connection state | | .taizn/seller/ | Dedicated human-owned Chrome profile | | .taizn/build/ | Generated package staging and output |

Config

{
  "build": {
    "command": ["pnpm", "build"],
    "output": "dist",
    "requiredFiles": ["main.css", "main.js"]
  },
  "signing": {
    "certificateDir": ".taizn/certificates",
    "profile": "my-tizen-profile"
  },
  "widget": {
    "configXml": "platforms/tizen/config.xml",
    "indexHtml": "platforms/tizen/index.html",
    "injectWebapis": true,
    "rewriteAssetUrls": false,
    "variants": {
      "development": {
        "applicationId": "ExampleDev.app",
        "bundleName": "example-dev",
        "icon": "platforms/tizen/icons/dev.png",
        "name": "Example Dev",
        "packageId": "ExampleDev"
      },
      "production": {
        "applicationId": "Example.app",
        "bundleName": "example",
        "icon": "platforms/tizen/icon.png",
        "indexHtml": "platforms/tizen/hosted.html",
        "injectWebapis": true,
        "name": "Example",
        "packageId": "Example",
        "rewriteAssetUrls": false
      }
    }
  }
}

Variant indexHtml, injectWebapis, and rewriteAssetUrls values override the top-level widget values. Variant excludeFiles values are added to top-level widget.excludeFiles. Use them when development packages should bundle local app assets but production packages should load hosted asset URLs.

Automation

Prefer JSON and artifacts when taizn feeds another tool:

pnpm exec taizn describe
pnpm exec taizn check --json --fields targets,tools.sdb
pnpm exec taizn prove --dry-run --json --fields application.id,target Example.app
pnpm exec taizn prove --json --artifact .taizn/proof.json Example.app
pnpm exec taizn prepare submission --json --artifact .taizn/submission.json package.wgt
pnpm exec taizn validate submission --json --fields ok,problems
pnpm exec taizn seller login --dry-run --json
pnpm exec taizn seller apps list --json --artifact .taizn/seller-apps.json
pnpm exec taizn tv doctor --connect --json --artifact .taizn/tv-doctor.json

Use --dry-run before mutating platform state when the command supports it. Artifact paths must stay inside the app directory; .taizn/... is the normal home for local proof state. Existing parent and destination symlinks must resolve inside the physical app directory; dangling links are rejected. Symlinked app checkouts and internal links are supported. This checks the filesystem before writing; it does not isolate writes from concurrent filesystem changes.

Command Surface

| Command | Purpose | | ------------------------------------ | -------------------------------------------------- | | describe | Print the machine-readable command surface | | check | Verify Tizen CLI, sdb, and target readiness | | apps | List installed target applications | | launch | Start an already-installed app | | prove | Resolve, launch, and record installed-app proof | | inspect wgt | Read neutral .wgt archive metadata | | prepare submission | Create a deterministic signed-WGT manifest | | validate submission | Check generic package metadata | | probe hosted-assets | Discover or probe hosted asset URLs | | logs capture | Record a bounded sdb dlog -d snapshot | | targets list / targets current | Report configured and connected target state | | profile | Import local Tizen signing certificates | | package | Build and sign a .wgt | | install | Package and sideload the widget | | run | Launch the configured variant application | | seller login | Open the human-owned Seller Office browser profile | | seller apps list | Read sanitized Seller Office application status | | tv doctor / tv info | Inspect Samsung TV remote-control readiness | | tv pair / tv press / tv script | Pair and send Samsung remote-control key sequences |

See Samsung TV Remote for pairing, environment, and limits.

Environment

Copy .env.example into .taizn/.env or export values in the shell:

TAIZN_CERT_PASSWORD=...
TAIZN_DIST_PASSWORD=...
TAIZN_VARIANT=development
TAIZN_TARGET=<tv-ip>:26101
TAIZN_TIZEN_CLI=~/tizen-studio/tools/ide/bin/tizen
TAIZN_SDB=~/tizen-studio/tools/sdb
TAIZN_SELLER_BROWSER=/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
TAIZN_TV_HOST=<tv-ip>
TAIZN_TV_PORT=8002
TAIZN_TV_PROTOCOL=wss
TAIZN_TV_TOKEN=<paired-remote-token>

taizn tv uses TAIZN_TV_HOST, or the host part of TAIZN_TARGET when no TV host is set. taizn tv pair writes the paired remote token to .taizn/remote.json; keep .taizn/ ignored.

taizn seller login opens a dedicated visible Chrome profile under .taizn/ and stores only its localhost DevTools port in .taizn/seller.json. Complete Samsung login yourself; Taizn does not request or read passwords, cookies, MFA, or browser tokens. See Seller Office for the supported read-only workflow and recovery steps.

Boundaries

taizn owns platform mechanics: Tizen CLI, sdb, widget archives, local submission preparation, Samsung remote keys, target inventory, logs, hosted-asset probes, and proof artifacts. Consumer apps own product journeys, credentials, app IDs, content IDs, account state, visual assertions, release decisions, and Samsung TV Seller Office portal mutations. Taizn's Seller Office surface is limited to a human-owned local browser session and sanitized read-only discovery.

Docs

Repo Internals

License

MIT