executable-metadata
Advanced tools
@@ -10,7 +10,4 @@ name: ci | ||
| os: | ||
| - ubuntu-16.04 | ||
| - ubuntu-latest | ||
| - macos-10.15 | ||
| - macos-latest | ||
| - windows-2016 | ||
| - windows-latest | ||
@@ -21,2 +18,4 @@ node: | ||
| - 14 | ||
| - 16 | ||
| - 17 | ||
| name: source-${{ matrix.os }}-node-${{ matrix.node }} | ||
@@ -23,0 +22,0 @@ runs-on: ${{ matrix.os }} |
+7
-0
@@ -5,2 +5,9 @@ # Changelog | ||
| ### [0.1.2](https://github.com/Anadian/executable-metadata/compare/v0.1.1...v0.1.2) (2022-01-11) | ||
| ### Continuous Integration | ||
| * Adding newer Nodes to CI. ([9cfa050](https://github.com/Anadian/executable-metadata/commit/9cfa050d32d677e0bb8c19baa4dfa42f8005c42b)) | ||
| ### [0.1.1](https://github.com/Anadian/executable-metadata/compare/v0.1.0...v0.1.1) (2021-03-01) | ||
@@ -7,0 +14,0 @@ |
@@ -12,7 +12,4 @@ { | ||
| "os": [ | ||
| "ubuntu-16.04", | ||
| "ubuntu-latest", | ||
| "macos-10.15", | ||
| "macos-latest", | ||
| "windows-2016", | ||
| "windows-latest" | ||
@@ -23,3 +20,5 @@ ], | ||
| 13, | ||
| 14 | ||
| 14, | ||
| 16, | ||
| 17 | ||
| ] | ||
@@ -26,0 +25,0 @@ } |
+12
-12
| { | ||
| "name": "executable-metadata", | ||
| "version": "0.1.1", | ||
| "version": "0.1.2", | ||
| "description": "Simply parse and print metadata from an executable binary's header from the command-line.", | ||
@@ -11,5 +11,5 @@ "main": "source/main.js", | ||
| "update-config": "hjson -j ci/github-actions.hjson | json2yaml --preserve-key-order -o .github/workflows/ci.yml", | ||
| "update-deps": "npm-check-updates -u", | ||
| "update-deps": "npm-check-updates -ux env-paths,ava", | ||
| "release": "standard-version", | ||
| "publish-release": "git push --follow-tags origin master && npm publish" | ||
| "publish-release": "git push --follow-tags origin main && npm publish" | ||
| }, | ||
@@ -52,18 +52,18 @@ "repository": { | ||
| "ava": "^3.15.0", | ||
| "coveralls": "^3.1.0", | ||
| "eslint": "^7.19.0", | ||
| "extract-documentation-comments": "^0.3.0", | ||
| "coveralls": "^3.1.1", | ||
| "eslint": "^8.6.0", | ||
| "extract-documentation-comments": "^0.3.11", | ||
| "hjson": "^3.2.2", | ||
| "npm-check-updates": "^11.1.1", | ||
| "npm-check-updates": "^12.1.0", | ||
| "nyc": "^15.1.0", | ||
| "standard-version": "^9.1.0" | ||
| "standard-version": "^9.3.2" | ||
| }, | ||
| "dependencies": { | ||
| "application-log-winston-interface": "^1.0.5", | ||
| "command-line-args": "^5.1.1", | ||
| "application-log-winston-interface": "^2.0.5", | ||
| "command-line-args": "^5.2.0", | ||
| "command-line-usage": "^6.1.1", | ||
| "concise-buffer": "0.0.3", | ||
| "env-paths": "^2.2.0", | ||
| "get-stream": "^6.0.0", | ||
| "lodash": "^4.17.20", | ||
| "get-stream": "^6.0.1", | ||
| "lodash": "^4.17.21", | ||
| "make-dir": "^3.1.0" | ||
@@ -70,0 +70,0 @@ }, |
+4
-4
@@ -5,5 +5,5 @@ # executable-metadata | ||
| [](https://conventionalcommits.org) | ||
| [](https://github.com/Anadian/executable-metadata/blob/master/LICENSE) | ||
| [](https://github.com/Anadian/executable-metadata/blob/main/LICENSE) | ||
| [](https://github.com/Anadian/executable-metadata/actions?query=workflow%3Aci) | ||
| [](https://coveralls.io/github/Anadian/executable-metadata?branch=master) | ||
| [](https://coveralls.io/github/Anadian/executable-metadata?branch=main) | ||
| [](https://www.npmjs.com/package/executable-metadata) | ||
@@ -22,3 +22,3 @@  | ||
| # Background | ||
| This was more of a research experiment than anything else. `executable-metadata` is a command-line application and NodeJS module for parsing metadata from the headers of Unix [ELF](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format) and Windows [PE](https://en.wikipedia.org/wiki/Portable_Executable) formatted executable binaries. Really, making this was just an excuse for me to learn the formats but it does work and it may be useful if you ever find yourself specifically needing high-level information on executeables in a strictly NodeJS environment: as unlikely as that may be. It returns parsed metadata in a simple JSON object so it can easily be converted or formatted however you need. When doing things outside of a pure NodeJS is acceptable, you may be better off using an existing command-line tool for parsing executable files; for example, [readelf](https://en.wikipedia.org/wiki/Readelf) can tell you far more about a given ELF than this can. | ||
| This was more of a research experiment than anything else. `executable-metadata` is a command-line application and NodeJS module for parsing metadata from the headers of Unix [ELF](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format) and Windows [PE](https://en.wikipedia.org/wiki/Portable_Executable) formatted executable binaries. Really, making this was just an excuse for me to learn the formats but it does work and it may be useful if you ever find yourself specifically needing high-level information on executables in a strictly NodeJS environment: as unlikely as that may be. It returns parsed metadata in a simple JSON object so it can easily be converted or formatted however you need. When doing things outside of a pure NodeJS is acceptable, you may be better off using an existing command-line tool for parsing executable files; for example, [readelf](https://en.wikipedia.org/wiki/Readelf) can tell you far more about a given ELF than this can. | ||
| # Install | ||
@@ -67,3 +67,3 @@ To use it as a dependency in a NodeJS project, run: | ||
| # License | ||
| MIT ©2021 Anadian | ||
| MIT ©2021-2022 Anadian | ||
@@ -70,0 +70,0 @@ SEE LICENSE IN [LICENSE](LICENSE) |
+7
-4
@@ -1,2 +0,2 @@ | ||
| #!/usr/local/bin/node | ||
| #!/usr/bin/env node | ||
| 'use strict'; | ||
@@ -1173,5 +1173,8 @@ /* jshint esversion: 6 */ | ||
| } | ||
| function_return = ApplicationLogWinstonInterface.InitLogger('debug.log', EnvironmentPaths.log); | ||
| if( function_return[0] === 0 ){ | ||
| setLogger( function_return[1] ); | ||
| try{ | ||
| function_return = ApplicationLogWinstonInterface.initWinstonLogger('debug.log', EnvironmentPaths.log); | ||
| setLogger( function_return ); | ||
| } catch(error){ | ||
| return_error = new Error(`ApplicationLogWinstonInterface.initWinstonLogger threw an error: ${error}`); | ||
| console.error(return_error); | ||
| } | ||
@@ -1178,0 +1181,0 @@ Logger.log({process: PROCESS_NAME, module: MODULE_NAME, file: FILENAME, function: FUNCTION_NAME, level: 'debug', message: 'Start of execution block.'}); |
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
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance 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
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
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance 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
97122
0.33%1647
0.18%+ Added
- Removed
Updated
Updated
Updated