Gathering detailed insights and metrics for @types/karma-chrome-launcher
Gathering detailed insights and metrics for @types/karma-chrome-launcher
Gathering detailed insights and metrics for @types/karma-chrome-launcher
Gathering detailed insights and metrics for @types/karma-chrome-launcher
The repository for high quality TypeScript type definitions.
npm install @types/karma-chrome-launcher
Typescript
Module System
96.6
Supply Chain
64.3
Quality
75.4
Maintenance
100
Vulnerability
100
License
TypeScript (99.84%)
JavaScript (0.15%)
Shell (0.01%)
Total Downloads
13,501,055
Last Day
2,052
Last Week
39,275
Last Month
174,780
Last Year
2,165,603
NOASSERTION License
49,996 Stars
89,698 Commits
30,433 Forks
641 Watchers
6 Branches
9,957 Contributors
Updated on Jul 04, 2025
Latest Version
3.1.4
Package Id
@types/karma-chrome-launcher@3.1.4
Unpacked Size
3.69 kB
Size
1.77 kB
File Count
5
Published on
Nov 07, 2023
Cumulative downloads
Total Downloads
Last Day
-8.3%
2,052
Compared to previous day
Last Week
-8%
39,275
Compared to previous week
Last Month
-5.7%
174,780
Compared to previous month
Last Year
-31.6%
2,165,603
Compared to previous year
1
npm install --save @types/karma-chrome-launcher
This package contains type definitions for karma-chrome-launcher (https://github.com/karma-runner/karma-chrome-launcher#readme).
Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/karma-chrome-launcher.
1import "karma"; 2 3declare module "karma" { 4 interface CustomLauncher { 5 /** 6 * The `--user-data-dir` is set to a temporary directory, 7 * but can be overridden on a custom launcher as shown below. 8 * One reason to do this is to have a permanent Chrome user data directory inside the project directory 9 * to be able to install plugins there (e.g. JetBrains IDE Support plugin). 10 */ 11 chromeDataDir?: string | undefined; 12 } 13} 14
These definitions were written by Piotr Błażejewicz (Peter Blazejewicz).
No vulnerabilities found.
Reason
30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
0 existing vulnerabilities detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 25/29 approved changesets -- score normalized to 8
Reason
dependency not pinned by hash detected -- score normalized to 8
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2025-06-30
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