Version updated for https://github.com/ext/npm-pkg-lint to version v4.6.5. This action is used across all versions by 35 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary The NPM Package Linting GitHub Action is an opinionated linter designed to validate and enforce best practices for NPM package tarballs and package.json metadata. It automates the detection of common issues, such as unnecessary files in package tarballs, improper metadata configurations, and outdated Node.js versions, helping developers create cleaner, more efficient packages. Its key capabilities include customizable rules for dependency allowances, file inclusion, and version checks, as well as integration with CI/CD workflows via GitHub Actions.

Version updated for https://github.com/ext/npm-pkg-lint to version v4.6.4. This action is used across all versions by 35 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary The NPM Package Linting GitHub Action is an opinionated linter designed to validate and enforce stricter standards for NPM package tarballs and package.json metadata. It automates the detection of common issues, such as invalid metadata, unnecessary files in package tarballs, and non-optimal dependency configurations, ensuring cleaner, more efficient NPM packages. Key capabilities include customizable validation rules, support for specifying target files, and seamless integration with CI pipelines via GitHub Actions.

Version updated for https://github.com/ext/npm-pkg-lint to version v4.6.3. This action is used across all versions by 35 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action, npm-pkg-lint, is an opinionated linter designed to validate and enforce best practices for NPM package tarballs and package.json metadata. It automates the detection of common issues, such as unnecessary files in package tarballs, outdated Node.js versions, and improper dependency structures, ensuring that packages adhere to strict standards for better tooling and efficiency. The action offers features like customizable dependency allowances, tarball and metadata validation, and automatic npm pack execution to streamline the publishing process for NPM packages.