npmpackage.info

Gathering detailed insights and metrics for grunt-packlock

grunt-packlock - 0.0.5 | npmpackage.info

grunt-packlock

Whiteliste allowed node packages

0.0.5

JavaScript

2.7

Installations

npm install grunt-packlock

Developer Guide

BETA

Typescript

No

Module System

CommonJS

NPM Version

1.4.6 Pull Requests

Open

0

Total

1

Closed

0

Merged

1

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

Shell

JavaScript (91.53%)

Shell (8.47%)

Developer

eoftedal

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

10 Commits

1 Forks

2 Watchers

1 Branches

1 Contributors

Updated on Feb 07, 2023

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

0.0.5

Package Id

grunt-packlock@0.0.5

Size

2.26 kB

NPM Version

1.4.6

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

grunt packlock

Peer Dependencies

grunt

Lockdown your modules by specifying a list of approved modules and versions (with semver). Packlock will scan against this list and report modules that are unapproved or at an unapproved version.

Grunt config

Install:

1npm install grunt-retire --save-dev

Add to your gruntfile:

1grunt.loadNpmTasks('grunt-packlock');

Config

1		packlock: {
2			scan: {
3				options: {
4					whitelist: 'test/packlock.json',
5					recurse: true
6				}
7			}
8		}

Specifying the policy

The policy consists of a simple .json file containing modules and versions. Semver is used to check version so you can use ranges etc. as specified on the semver page.

{
    "commander": "^2.2.0",
    "read-installed": "^2.0.3"
}

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

License

Determines if the project has defined a license.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

2.7

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More