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

@armakuni/circleci-context-validator

v0.1.7

Published

Circle Context Validation in Code

Readme

CircleCI Context Validator CLI Tool

CircleCI

Purpose

As projects grow, team members drop in and out and the documented state of environment variables become a mystery, and left in a precarious state not knowing if a varaible is required any more looking at the Circle UI.

CircleCI Context Validator (CCV for short) makes use of a simple yaml configuration file, refer to the example. The configuration file refers to the names of the context and associated environment variables. The config should reflect what should only be present in your context (can be more than one, should you need that), is then compared against the API giving back user input on valid or failures.

Prerequisites

Install

$ npm install -g @armakuni/circleci-context-validator

or

$ yarn global add @armakuni/circleci-context-validator

Commands

$ ccv (--version)
@armakuni/circleci-context-validator/<semver> darwin-x64 node-v16.13.1
$ ccv --help [COMMAND]
USAGE
  $ CIRCLECI_PERSONAL_ACCESS_TOKEN=example-token ccv circleci validate --context-definitions example/context_validator.yml
USAGE
  $ ccv help [COMMAND] [-n]

ARGUMENTS
  COMMAND  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for ccv.

Examples

Run the CLI tool:

CIRCLECI_PERSONAL_ACCESS_TOKEN=example-token ccv circleci validate --context-definitions .circleci/context_validator.yml

example cli usage

All Valid

Context exists, associated env var values configured exist in context definition yaml.

Context "context-validator-ci" is valid
Success

Missing Env Var

Configured in context definition yaml, but not present in CircleCI Context

Missing Env Var "API_KEY" in Context "context-validator-ci"
Failures 1

Missing Context

Configured in context definition yaml, but not present in CircleCI Context

Context "context-validator-cid" is missing
Failures 1

Undocumented

A value is not configured, but exists in circleci

Unexpected Env Var "NPM_TOKEN" in Context "context-validator-ci"
Failures 1

Development

How to dev on circleci-context-validator, for a quick start guide checkout oclif which this tool makes heavy use of.

Entrypoint

Command entrypoint is located: circleci-context-validator/src/commands/circleci/validate

NVM

$ cd circleci-context-validator
$ nvm use .

Dev Run (no compile)

CIRCLECI_PERSONAL_ACCESS_TOKEN=generate_personal_access_token bin/dev circleci validate --context-definitions example/context_validator.yml

Upcoming

  • Pretty console output
  • Different output formats e.g. JSON
  • Support for standard Environment Variables i.e. non-context associated
  • Autocomplete commands
  • Retrieve existing context and associated env vars to pre-populate a context_validator.yml