@vitest/mocker
Advanced tools
+10
-5
| { | ||
| "name": "@vitest/mocker", | ||
| "type": "module", | ||
| "version": "4.1.0-beta.5", | ||
| "version": "4.1.0-beta.6", | ||
| "description": "Vitest module mocker implementation", | ||
| "license": "MIT", | ||
| "funding": "https://opencollective.com/vitest", | ||
| "homepage": "https://github.com/vitest-dev/vitest/tree/main/packages/mocker#readme", | ||
| "homepage": "https://github.com/vitest-dev/vitest/tree/main/packages/mocker", | ||
| "repository": { | ||
@@ -17,2 +17,7 @@ "type": "git", | ||
| }, | ||
| "keywords": [ | ||
| "vitest", | ||
| "test", | ||
| "mock" | ||
| ], | ||
| "sideEffects": false, | ||
@@ -76,3 +81,3 @@ "exports": { | ||
| "magic-string": "^0.30.21", | ||
| "@vitest/spy": "4.1.0-beta.5" | ||
| "@vitest/spy": "4.1.0-beta.6" | ||
| }, | ||
@@ -87,4 +92,4 @@ "devDependencies": { | ||
| "vite": "^6.3.5", | ||
| "@vitest/utils": "4.1.0-beta.5", | ||
| "@vitest/spy": "4.1.0-beta.5" | ||
| "@vitest/spy": "4.1.0-beta.6", | ||
| "@vitest/utils": "4.1.0-beta.6" | ||
| }, | ||
@@ -91,0 +96,0 @@ "scripts": { |
+2
-0
| # @vitest/mocker | ||
| [](https://npmx.dev/package/@vitest/mocker) | ||
| Vitest's module mocker implementation. | ||
| [GitHub](https://github.com/vitest-dev/vitest/blob/main/packages/mocker/) | [Documentation](https://github.com/vitest-dev/vitest/blob/main/packages/mocker/EXPORTS.md) |
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
186821
0.09%8
33.33%+ Added
- Removed
Updated