ligolang - npm Package Compare versions

Comparing version 0.57.0-dev.linux.1 to 0.57.0-dev.macos-intel.1

package.json

 {
   "name": "ligolang",
-  "version": "0.57.0-dev.linux.1",
+  "version": "0.57.0-dev.macos-intel.1",
   "description": "A friendly Smart Contract Language for Tezos",
   "os": [
-    "linux"
+    "darwin"
   ],
@@ -13,6 +13,8 @@ "cpu": [
   "repository": "https://gitlab.com/ligolang/ligo",
-  "scripts": {},
+  "scripts": {
+    "postinstall": "node -e \"process.env['OCAML_VERSION']='ocaml'; process.env['OCAML_PKG_NAME']='n.00.0000'; process.env['ESY_RELEASE_REWRITE_PREFIX']=true; require('./esyInstallRelease.js')\""
+  },
   "bin": {
-    "ligo": "bin/ligo.exe"
+    "ligo": "bin/ligo"
   }
 }

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

Install scripts

Supply chain risk

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Found 1 instance in 1 package

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 6 instances in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Shell access

Supply chain risk

This 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 risk

Package 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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 4 instances in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 2 instances 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

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

126665458

increased by24.39%

Number of package files

12

increased by300%

Lines of code

11465

increased byInfinity%

Worsened metrics

Number of high supply chain risk alerts

1

increased byInfinity%

Number of low supply chain risk alerts

15

increased by1400%

Number of medium supply chain risk alerts

14

increased by250%

No dependency changes