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

@appport/assessment

v0.1.0

Published

AppWorks existing-application assessment: a static, read-only, evidence-backed capability inventory of a repository as an appport.application-assessment/1 artifact. Executes nothing and grants no authority.

Readme

@appport/assessment

AppWorks existing-application assessment. It reads a repository statically and writes an appport.application-assessment/1 artifact. The artifact is an evidence-backed inventory of the business capabilities the application exposes, how they are implemented, what they read, write and call, how they are authorized, validated and tested, and which one is the most reasonable first candidate for AppPort exposure. Specification: spec/assessment-1.md in rkendel1/appworks. JSON Schema ships in schemas/.

The appworks command comes with @appport/extraction. This package alone installs appworks-assess, which takes the same assess and verify commands.

appworks assess ./memos --output memos-assessment.json     # exit 0 (complete or partial), 1 fatal, 2 usage, 3 --strict and partial
appworks verify memos-assessment.json --repo ./memos       # integrity, honesty, and every observed location against the files
import { assessRepository, verifyAssessment } from "@appport/assessment";

const assessment = assessRepository("./memos");
assessment.recommendation;            // { candidate, reasons, ranking, beforeExposure } or null
verifyAssessment(assessment, { repository: "./memos" });

| Export | Purpose | |---|---| | assessRepository | the assessment; options for limits, thresholds and (for tests) volatile metadata | | verifyAssessment | structure, evidence classes and references, verified/authority claims, digest; locations with repository | | assessmentDigest, evidenceId | the content rules (digestOf of @appport/protocol) | | proposeCapabilityName, messageSchema | the AppPort proposal rules | | types and constants | ApplicationAssessment, Evidence, Candidate, ProposedCapability, ASSESSMENT_FORMAT, EVIDENCE_CLASSES, READINESS_CLASSES, … |

Supported: Protocol Buffers services with google.api.http, and Go (handlers, call graph, SQL literals, status codes, goroutines, outbound net/http, configuration keys, tests). go.mod and package.json are read as manifests. Other languages are counted and reported, and make an assessment partial.

Scanner 2 (assessRepository(path, { scanner: 2 }), appworks assess --scanner 2, format appport.application-assessment/2) also reads the HTTP routes a JavaScript or TypeScript application registers (Express, Fastify, Koa router, Hono, NestJS), with the prefixes of the mounts that lead to each, the middleware in front of it and, where one exists, its handler's definition. A route is evidence that an entry point exists and nothing more: no handler body is read and no shape is assumed, so a route is investigate at best, is never recommended, and cannot yet be extracted. Scanner 1 is the default and its output is unchanged, so existing digests still reproduce. See spec/assessment-1.md §11.

Guarantees: it never writes to, executes, builds or imports anything in the target; it never follows symbolic links; it uses no network and no language model. Every observed fact has a location you can check; every inference names its basis; what it cannot determine is recorded as unknown. It never claims verified behavior, grants no authority, registers nothing, and its proposed capability is not a contract. Depends only on @appport/protocol 1.3.0. Part of the AppPort ecosystem, not of the AppPort protocol. Not implemented: extraction, compilation, execution and migration.