JSPM

@lavamoat/git-safe-dependencies

0.1.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 125037
  • Score
    100M100P100Q180167F
  • License MIT

Opinionated dependency linter for your git/github dependencies

Package Exports

  • @lavamoat/git-safe-dependencies
  • @lavamoat/git-safe-dependencies/src/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@lavamoat/git-safe-dependencies) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

git-safe-dependencies

WARNING: This is an alpha version. The opinions are still forming and anything can change at any time. Test coverage is incomplete. Use at your own risk.

Validate your package.json and lockfile (NPM, Yarn classic or Yarn Berry) against an opinionated set of rules around using git dependencies that we at LavaMoat recommend.
No configuration, no excuses.

Installation

You can install @lavamoat/git-safe-dependencies using npm:

npm install --save-dev @lavamoat/git-safe-dependencies

Usage

git-safe-dependencies [--type=yarn|npm] [--ignore=file.json] [--projectRoot=path]
  • --type=npm|yarn - Specify the type of lockfile to lint if it's not obvious from the file name. Supported values are dictated by lockfile-lint package.
  • --ignore=file.json - Specify a JSON file with a list of problem IDs to ignore (if you must). Keep the file version controlled to track who ignored what and why.
  • --projectRoot=path - Specify the root of the project to lint. Defaults to the current working directory.

Programmatic usage

WIP, but do try :)

const gitSafeDependencies = require('@lavamoat/git-safe-dependencies')

TODO: design a more granular programmatic API