+5
-0
@@ -0,1 +1,6 @@ | ||
| ## 1.2.3 | ||
| * [javascript: fix require()'ing files inside a package (#147)](https://github.com/extremeheat/JSPyBridge/commit/a93fce586c4ad3d37d3a58710fd934523df94038) (thanks @livinNector) | ||
| * [doc: fix some typos, optimize wording (#160)](https://github.com/extremeheat/JSPyBridge/commit/12455b31875d292626d6056d4aa365b7449783fb) (thanks @mk-pmb) | ||
| * [readme: pip3 -> pip](https://github.com/extremeheat/JSPyBridge/commit/13e6d9ff5bea9f494b5d9d35c6afaac27a678daa) (thanks @extremeheat) | ||
| ## 1.2.2 | ||
@@ -2,0 +7,0 @@ * [Handle non-Error objects thrown in JS (#154)](https://github.com/extremeheat/JSPyBridge/commit/5b3aecd787fb2bb531079b61f8492a92f633eaff) (thanks @extremeheat) |
+1
-1
@@ -5,3 +5,3 @@ { | ||
| "description": "Bridge to call and interop Python APIs from Node.js", | ||
| "version": "1.2.2", | ||
| "version": "1.2.3", | ||
| "main": "./src/pythonia/index.js", | ||
@@ -8,0 +8,0 @@ "types": "./src/pythonia/index.d.ts", |
+4
-4
@@ -32,3 +32,3 @@ # JSPyBridge | ||
| ```sh | ||
| pip3 install javascript | ||
| pip install javascript | ||
| ``` | ||
@@ -322,6 +322,6 @@ | ||
| * The `ffid` keyword is reserved. You cannot use it in variable names, object keys or values as this is used to internlly track objects. | ||
| * The `ffid` keyword is reserved. You cannot use it in variable names, object keys, or values, as this is used to internally track objects. | ||
| * On the bridge to call JavaScript from Python, due to the limiatations of Python and cross-platform IPC, we currently communicate over standard error which means that specific output in JS standard error can interfere with the bridge (as of this writing, the prefices `{"r"` and `blob!` are reserved). A similar issue exists on Windows with Python. You are however very unlikely to have issues with this. | ||
| * On the bridge to call JavaScript from Python, due to the limitations of Python and cross-platform IPC, we currently communicate over standard error which means that specific output in JS standard error can interfere with the bridge. (Currently, the prefixes `{"r"` and `blob!` are reserved.) A similar issue exists on Windows with Python. You are however very unlikely to have issues with this. | ||
| * Function calls will timeout after 100000 ms and throw a `BridgeException` error. That default value can be overridden by defining the new value of `REQ_TIMEOUT` in an environment variable, and setting it to 0 will disable timeout checks. | ||
| * Function calls will timeout after 100000 ms (100 sec) and throw a `BridgeException` error. That default value can be overridden by defining an environment variable `REQ_TIMEOUT`. Setting it to 0 will disable timeout checks. |
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary 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 4 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
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
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary 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 4 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
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
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
528607
0.09%