node-peruse - npm Package Compare versions

Comparing version 1.3.2 to 1.4.2

bin/peruse.js

@@ -13,2 +13,3 @@ #!/usr/bin/env node
   validateDocker,
+  validateGitCommits,
 } from '../src/index.js';
@@ -30,3 +31,3 @@ import { logger } from '../src/logger.js';
 program
-  .version('1.3.1')
+  .version('1.3.2')
   .description('A CLI tool for analyzing Node.js applications')
@@ -40,3 +41,4 @@ .option('-d, --dependencies', 'Analyze dependencies')
   .option('-os, --name', 'Detect os name')
-  .option('-dok, --dockerfile', 'Dockerfile validator');
+  .option('-dok, --dockerfile', 'Dockerfile validator')
+  .option('-g, --git', 'Validate Git commit best practices');
 
@@ -79,2 +81,6 @@ program.parse(process.argv);
   }
+
+  if (options.git) {
+    await runTask('Validating Git commits', validateGitCommits);
+  }
 })();

package.json

 {
   "name": "node-peruse",
-  "version": "1.3.2",
+  "version": "1.4.2",
   "description": "A powerful CLI tool designed to analyze your node.js application.",
@@ -5,0 +5,0 @@ "main": "src/index.js",

README.md

@@ -17,6 +17,8 @@ <div align="center">
 
-- Analyze project dependencies
+- Validate dockerfiles
+- Git commit best practices Validator
 - Check outdated dependencies
 - Check Node.js version
 - Check system memory usage
+- Analyze project dependencies
 
@@ -42,12 +44,20 @@ There are many more features to come, so keep on eye on this repository.
 
-### 1. Analyze project dependencies
+### 1. Check or validate dockerfiles
 
-Use the `--dependencies` option to analyze and list all dependencies in your project.
+Find issues in your dockerfiles (e.g., Dockerfile, compose.yml), use the `--dockerfile` flag.
 
 ```bash
-node-peruse --dependencies
+node-peruse --dockerfile
 ```
 
-### 2. Check outdated dependencies
+### 2. Git commit best practices validator
 
+This feature scans recent Git commits to ensure they follow best practices: (e.g., feat:, fix:, chore:, etc.)
+
+```bash
+node-peruse --git
+```
+
+### 3. Check outdated dependencies
+
 To check outdated packages in your project, use the `--outdated` flag.
@@ -59,3 +69,3 @@
 
-### 3. Check Node.js version
+### 4. Check Node.js version
 
@@ -68,3 +78,3 @@ To check node.js version, use the `--node-check` flag.
 
-### 4. Check system memory usage
+### 5. Check system memory usage
 
@@ -77,3 +87,3 @@ To check system memory is sufficient, use the `--memory-check` flag.
 
-### 5. Check unused dependencies
+### 6. Check unused dependencies
 
@@ -86,3 +96,3 @@ To check unused dependencies in you node.js application, use the `--unused` flag.
 
-### 6. Check your os architecture
+### 7. Check your os architecture
 
@@ -95,3 +105,3 @@ To get os architecture, use the `--arch` flag.
 
-### 7. Check your os name
+### 8. Check your os name
 
@@ -104,8 +114,8 @@ To get your os name, use the `--name` flag.
 
-### 8. Check or validate dockerfiles
+### 9. Analyze project dependencies
 
-Find issues in your dockerfiles (e.g., Dockerfile, compose.yml), use the `--dockerfile` flag.
+Use the `--dependencies` option to analyze and list all dependencies in your project.
 
 ```bash
-node-peruse --dockerfile
+node-peruse --dependencies
 ```
@@ -112,0 +122,0 @@

src/index.js

@@ -7,1 +7,2 @@ export * from './depCheck.js';
 export * from './dockerfileValidator.js';
+export * from './gitValidate.js';

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

16684

increased by11.23%

Number of package files

14

increased by7.69%

Lines of code

318

increased by13.17%

Number of lines in readme file

133

increased by8.13%

Worsened metrics

Number of medium supply chain risk alerts

2

increased by100%

No dependency changes