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

effect-build-sbom

v0.8.0

Published

Effect-native SPDX and CycloneDX SBOM generation with Syft.

Readme

effect-build-sbom

Generate SPDX 2.3 or CycloneDX 1.6 JSON software bills of materials for release artifacts with Syft, as Effect programs.

npm install --save-dev --save-exact [email protected] [email protected] @effect/[email protected] @effect/[email protected]

Syft 1.50 or newer must be installed.

Usage

import { Effect } from "effect";
import { Artifact } from "effect-build";
import * as Sbom from "effect-build-sbom";

const sbom = (executable: Artifact.Executable) =>
  Effect.gen(function*() {
    const lockfile = yield* Artifact.file("package-lock.json", { name: "hello", version: "1.0.0" });
    return yield* Sbom.generate({
      subject: executable,
      source: lockfile,
      format: "cyclonedx-json",
      outfile: "dist/hello.cdx.json",
    });
  }).pipe(Effect.provide(Sbom.layer()));

generate({ subject, source?, format, outfile, cwd?, atomic?, onExists?, prefix? }) returns the SBOM as an Artifact.File. format is spdx-json or cyclonedx-json.

  • subject is the release artifact the inventory describes: any core artifact. Without source, Syft scans the subject at its original path, so filename-based detection still works.
  • source is a source directory or a named lockfile. When given, Syft scans it instead of the subject, which is how a compiled TypeScript executable gets an inventory of the dependencies that were bundled into it. Include the manifests and lockfiles Syft supports.

A successful scan means Syft wrote an inventory of the packages it could discover. It does not establish completeness: a compiled executable can yield zero packages even when it embeds Effect, and a source scan can list dependencies the bundler dropped or miss lockfile formats Syft does not read. Empty package lists are valid output. Keep the relationship between the source you scanned and the artifact you shipped in your release records.

Versions and errors

Sbom.layer({ executable?, version? }) resolves Syft once; Sbom.supported is >=1.50.0 <2.0.0 and Sbom.tested is 1.50.0. Sbom.GenerateError is Tool.InputInvalid, Artifact.ArtifactError, Tool.Failed, Tool.SpawnFailed, or Commit.CommitError.

Recipes · Tools and providers · Errors and checks