blessed - npm Package Compare versions

Comparing version 0.0.3 to 0.0.4

package.json

@@ -5,10 +5,12 @@ {
   "author": "Christopher Jeffrey",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "main": "./lib/program.js",
+  "bin": "./bin/tput.js",
+  "preferGlobal": false,
   "repository": "git://github.com/chjj/blessed.git",
   "homepage": "https://github.com/chjj/blessed",
   "bugs": { "url": "http://github.com/chjj/blessed/issues" },
-  "keywords": ["curses", "tui"],
-  "tags": ["curses", "tui"],
+  "keywords": ["curses", "tui", "tput"],
+  "tags": ["curses", "tui", "tput"],
   "scripts": { "test": "node test", "bench": "node test --bench" }
 }

README.md

@@ -5,6 +5,5 @@ # blessed
 
-As of right now, it does not read all terminfo. It was designed for one
-terminal's terminfo: **xterm**, but if you understand the differences between
-the three popular vt100-based terminals (xterm, screen, rxvt), you should be
-able to use it for any terminal.
+Blessed was originally written to only support the xterm terminfo, but can
+now parse and compile any terminfo to be completely portable accross all
+terminals. See the `tput` example below.
 
@@ -16,3 +15,23 @@ I want this library to eventually become a high-level library for terminal
 
+This will actually parse the xterm terminfo and compile every
+string capability to a javascript function:
+
 ``` js
+var Tput = require('blessed').Tput
+  , tput = Tput('xterm');
+
+console.log(tput.setaf(4) + 'hello' + tput.sgr0());
+```
+
+To play around with it on the command line, it works just like tput:
+
+``` bash
+$ tput.js setaf 2
+$ tput.js sgr0
+$ echo "$(tput.js setaf 2)hello world$(tput.js sgr0)"
+```
+
+The higher level functionality is exposed in the main `blessed` module:
+
+``` js
 var blessed = require('blessed')
@@ -19,0 +38,0 @@ , program = blessed();

New alerts

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

Environment variable access

Supply chain risk

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

Found 1 instance in 1 package

Filesystem access

Supply chain risk

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

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

230908

207.34%

Number of package files

11

83.33%

Lines of code

4602

118.93%

Number of lines in readme file

111

20.65%

Worsened metrics

Number of low supply chain risk alerts

7

250%

Number of medium supply chain risk alerts

2

Infinity%

No dependency changes