tokenizer - npm Package Compare versions

Comparing version 0.1.1 to 0.1.2

lib/Tokenizer.js

@@ -65,3 +65,6 @@ var EventEmitter = require('events').EventEmitter;
     if(nobuffer) {
-        this._gotToken(data.substr(last_tokenized), matching[0]);
+        // when no actual data was tokenized, matching is undefined
+        if(matching) {
+            this._gotToken(data.substr(last_tokenized), matching[0]);
+        }
     }
@@ -75,3 +78,3 @@ // buffer data for the next write
 Tokenizer.prototype.end = function end(data) {
-    this.write(data || '', true);
+    if(data) this.write(data, true);
     this.write = noop;
@@ -78,0 +81,0 @@ this.emit('end');

package.json

 {
   "name": "tokenizer",
   "description": "A wide purpose tokenizer for node.js which looks like a stream",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "homepage": "http://github.com/floby/node-tokenizer",
@@ -6,0 +6,0 @@ "repository": {

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

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

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

Non-existent author

Supply chain risk

The package was published by an npm account that no longer exists.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

8213

increased by2.43%

Number of package files

7

increased by16.67%

Lines of code

162

increased by3.85%

Number of high supply chain risk alerts

0

decreased by-100%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes