New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

@chimp-stack/core

Package Overview
Dependencies
Maintainers
1
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@chimp-stack/core

> Shared configuration and environment loader for the growing chimp toolchain.

latest
Source
npmnpm
Version
0.4.7
Version published
Maintainers
1
Created
Source

🧠 @chimp-stack/core

Shared configuration and environment loader for the growing chimp toolchain.

npm version License: MIT CI

This package contains the core logic for reading .chimprc config files, loading environment variables, and handling shared behavior between tools like git-chimp, doc-chimp, and review-chimp.

📦 Installation

Install via npm:

npm install @chimp-stack/core

Or in a monorepo:

npm install --workspace=@chimp-stack/core

🛠 Usage

In your tool package (e.g., git-chimp, review-chimp), import and use the helpers:

import { loadChimpConfig, getEnv } from '@chimp-stack/core';

const config = loadChimpConfig('gitChimp');
const env = getEnv();

📁 Config File: .chimprc

This package looks for a .chimprc file in the current project or in your home directory (~/.chimprc).

{
  "gitChimp": {
    "model": "gpt-4",
    "tone": "dry sarcasm",
    "prMode": "draft"
  },
  "reviewChimp": {
    "severity": "high"
  }
}

The structure is namespaced per tool. You can override values via CLI flags if needed.

🏗 Exported Functions

FunctionDescription
loadChimpConfig(scope)Loads config for the given tool (gitChimp, docChimp, etc) from .chimprc
getEnv()Validates and returns required environment variables (e.g., OPENAI_API_KEY)
resolveChimpConfigPath()Returns the resolved file path of the active .chimprc

🧪 Development

Build

npm run build

This uses tsup to emit both ESM and CJS output to dist/.

Lint

npm run lint

🚀 Publishing

This package can be independently published from the monorepo (if applicable) using npm publish or through CI pipelines like semantic-release.

If used inside a Turborepo or other monorepo setup, make sure its package.json has a name field and correct main/exports paths for npm publishing.

🐒 Part of the Chimp Stack™

  • git-chimp – commit & PR generator
    source
  • doc-chimp – auto-documentation from commits and code source
  • review-chimp – coming soon: let the monkey do your code reviews
  • core – this package
    source

“Because even the best engineers deserve a monkey on their shoulder.”

FAQs

Package last updated on 30 Jun 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts