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

@finos/calm-schema

v1.3.0

Published

The CALM (Common Architecture Language Model) Meta Schema

Readme

FINOS - Graduated

CALM Schema

CALM (the Common Architecture Language Model) is a JSON Schema vocabulary for describing software architecture as data: the nodes that make up a system, the relationships between them, the interfaces they expose, the business flows that run across them, and the controls that govern them. A CALM document is a plain JSON file that validates against this schema, so it can be produced and consumed by tooling — generated from code, rendered as diagrams, checked in CI, or used to enforce architectural and compliance rules — rather than living only as a diagram in a slide deck.

  • Nodes — architecture components (systems, services, databases, actors) with properties, interfaces, and deployments
  • Relationships — connections between nodes (interacts, connects, deployed-in, composed-of)
  • Flows — business flows composed of ordered transitions across relationships, mapping business processes onto technical components
  • Controls — security and compliance requirements attached to nodes, relationships, or flows
  • Interfaces — modular interface definitions, either built in or externally defined
  • Metadata — free-form annotations on any schema element

Using the schema

The schema is published to npm as @finos/calm-schema:

npm install @finos/calm-schema

Each published version is immutable and corresponds to a git tag in this repository (e.g. v1.2). See CHANGELOG.md for what changed in each release. CALM tooling — including the CLI, CALM Hub, and the VS Code extension — depends on a specific published version of this package to validate CALM documents.

Each release is also served at the URL in its $id, for example https://calm.finos.org/release/1.2/meta/calm.json.

standards/ holds standards that extend the schema, for example the deployment decorator standard. Each standard has its own version and is served at https://calm.finos.org/standards/<name>/<version>/. The npm package does not include them.

Project repositories

CALM Schema is one of three repositories that make up the FINOS Architecture as Code project, also known as CALM:

| Repository | Contents | |------------|----------| | calm-governance | The governance home — project-wide governance, contribution guidelines, and Code of Conduct. Holds no code. | | calm-schema | This repository. The CALM Meta Schema, its documentation, and validation test suite. | | architecture-as-code | The main repository — CLI, server, shared libraries, data models, widgets, CALM Hub and its UI, the VS Code extension, and the documentation site. Depends on @finos/calm-schema published from this repository. |

Proposing a schema change

Schema changes are developed on feature branches and merged to main via pull request; main always holds the current, unreleased state of the schema. Merging to main does not publish anything by itself — it produces a release candidate that can accumulate further merged changes before a release is deliberately cut and published to npm as a separate, manually triggered step.

  1. Open a GitHub Issue using the Schema Change Proposal template, describing the motivation, the proposed change, and the impact on existing tooling.
  2. Once agreed, develop the change on a feature branch alongside updated validation tests. CI runs the schema test suite on every push.
  3. Open a pull request to main. It requires approval from a member of the calm-schema-governance team — see CONTRIBUTING.md.
  4. When maintainers decide to cut a release, publishing to npm and tagging the release is a separate, manually triggered step, kept deliberately outside of the merge process to avoid publishing a schema version prematurely. The publish workflow publishes the tag to npm and to calm.finos.org. Then it starts the schema compatibility workflow in architecture-as-code, which tests every CALM tool against the new version and opens an issue that names the tools that fail.

Contributing

For any questions, bugs or feature requests please open an issue For anything else please send an email to {project mailing list}.

To submit a contribution:

  1. Fork it (https://github.com/finos/calm-schema/fork)
  2. Create your feature branch (git checkout -b feature/fooBar)
  3. Read this repository's contribution guidelines, the project-wide contribution guidelines and the Community Code of Conduct
  4. Commit your changes (git commit -am 'Add some fooBar')
  5. Push to the branch (git push origin feature/fooBar)
  6. Create a new Pull Request

Changes to the schema require approval from a member of the calm-schema-governance team — see CONTRIBUTING.md.

NOTE: All pull requests to this repository require a signed CLA via EasyCLA. Read FINOS Contribution Requirements before contributing.

Questions about the CLA or EasyCLA? Email [email protected]

Governance

The project's governance policies, Maintainer roster and Code of Conduct are maintained in finos/calm-governance and apply across every repository in the project.

| Document | Covers | |---|---| | GOVERNANCE.md | Roles, contribution rules, Maintainer voting, and how Maintainers are added and removed | | MAINTAINERS.md | The project-wide Maintainer roster and the Lead Maintainer | | CONTRIBUTING.md | Project-wide contribution guidelines | | CODE_OF_CONDUCT.md | The Code of Conduct all participants are subject to |

A contributor must be nominated and approved by a vote of the existing Maintainers before they are granted write access to this repository, as set out in GOVERNANCE.md.

Support

Support is community-based and best-effort: ask in a GitHub issue in this repository. The project's SUPPORT.md states which schema releases are supported and when a release stops receiving security updates. To report a vulnerability privately, follow SECURITY.md, which also holds the dependency and code scanning policy and the instructions for verifying release integrity.

License

Copyright 2026 FINOS

Distributed under the Apache License, Version 2.0.

SPDX-License-Identifier: Apache-2.0