Gathering detailed insights and metrics for @virmator/deps
Gathering detailed insights and metrics for @virmator/deps
Centralize and automate all the things! So I don't have to copy pasta configs in every single project.
Installations
npm install @virmator/depsDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Min. Node Version
>=22
Node Version
22.15.0
NPM Version
11.4.1
Score
51.7
Supply Chain
68.1
Quality
90
Maintenance
100
Vulnerability
94.6
License
Releases
139
Languages
4
TypeScript
JavaScript
HTML
CSS
TypeScript (90.61%)
JavaScript (9.16%)
HTML (0.2%)
CSS (0.03%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
CC0-1.0 License
3 Stars
599 Commits
1 Watchers
2 Branches
1 Contributors
Updated on Jun 12, 2025
Maintainers
1
Package Meta Information
Latest Version
13.15.4
Package Id
@virmator/deps@13.15.4
Unpacked Size
42.05 kB
Size
9.47 kB
File Count
12
NPM Version
11.4.1
Node Version
22.15.0
Published on
Jun 07, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
@virmator/deps
A default plugin for virmator.
Available commands
-
deps
Various dependency commands. A sub-command must be provided.
-
Examples
- check import dependencies:
virmator deps check - upgrade npm dependencies:
virmator deps upgrade - regenerate npm dependencies:
virmator deps regen
- check import dependencies:
-
Sub Commands
-
check
Checks that import dependencies pass your dependency cruiser config. The base configuration blocks typical import errors such as circular dependencies and importing test files.
- Examples
virmator deps check
- Configs
- configs/dep-cruiser.config.cts
- Deps
- Examples
-
upgrade
Upgrades dependencies using npm-check-update. Does not automatically run 'npm i'. It is recommended to run 'virmator deps regen' instead.
- Examples
virmator deps upgrade
- Configs
- configs/ncu.config.ts
- Deps
- Examples
-
regen
Force regeneration of all all dependencies by deleting all node_modules directories and package-lock.json and then running 'npm i'.
- Examples
virmator deps regen
- Examples
-
-
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE-CC0:0
- Info: FSF or OSI recognized license: Creative Commons Zero v1.0 Universal: LICENSE-CC0:0
Reason
0 existing vulnerabilities detected
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tagged-release.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/electrovir/virmator/tagged-release.yml/dev?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tagged-release.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/electrovir/virmator/tagged-release.yml/dev?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/tagged-release.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/electrovir/virmator/tagged-release.yml/dev?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/electrovir/virmator/tests.yml/dev?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/electrovir/virmator/tests.yml/dev?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/tests.yml:30
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 1 out of 2 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: topLevel 'contents' permission set to 'write': .github/workflows/tagged-release.yml:8
- Warn: no topLevel permission defined: .github/workflows/tests.yml:1
- Info: no jobLevel write permissions found
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'dev'
Score
4.5
/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