segfault-handler - npm Package Compare versions

Comparing version 1.0.1 to 1.1.0

package.json

 {
   "name": "segfault-handler",
   "description": "catches SIGSEGV and prints diagnostic information",
-  "version": "1.0.1",
-  "author": "Dave Dopson <[e-mail]>",
+  "version": "1.1.0",
+  "author": "Kenneth Geisshirt <[e-mail]>",
   "contributors": [
@@ -10,3 +10,4 @@ "Dave Dopson <[e-mail]>",
     "David Swift <[e-mail]>",
-    "Anton Whalley <[e-mail]>"
+    "Anton Whalley <[e-mail]>",
+    "Kenneth Geisshirt <[e-mail]>"
   ],
@@ -22,3 +23,3 @@ "repository": {
   "main": "index.js",
-  "license": "SEE LICENSE IN README.md"
+  "license": "BSD-3-Clause"
 }

README.md

 # Overview
 
-This module is a critical tool for debugging Node.js C/C++ native code modules, and is safe to use in production environments.  Normally, when a bug is triggered in native code, the node process simply ends with no helpful information.  In production, this can manifest as worker processes restarting for seemingly no reason.  Running node in gdb is messy and infeasible for a production environment.  Instead this module will sit unobtrusively doing nothing (zero perf impact) as long as Node is well-behaved.  If a SIGSEGV signal is raised, the module will print a native stack trace to both STDERR and to a timestamped file (STDERR is usually ignored in production environments.  files are better).
+This module is a critical tool for debugging Node.js C/C++ native code modules, and is safe to use in production environments.  Normally, when a bug is triggered in native code, the node process simply ends with no helpful information.  In production, this can manifest as worker processes restarting for seemingly no reason.  Running node in gdb is messy and infeasible for a production environment.  Instead this module will sit unobtrusively doing nothing (zero perf impact) as long as Node is well-behaved.  If a SIGSEGV signal is raised, the module will print a native stack trace to both STDERR and to a timestamped file (STDERR is usually ignored in production environments; files are better).
 
@@ -20,3 +20,2 @@ Using the module is as simple as:
 SegfaultHandler.causeSegfault(); // simulates a buggy native module that dereferences NULL
-
 ```
@@ -61,14 +60,30 @@
 
-Now you can start debugging using tools like "objdump -dS module.node" to try and sort out what the stack actually means.  Sometimes, just identifying _which_ native module is causing problems is the biggest win.
+Now you can start debugging using tools like `objdump -dS module.node` to try and sort out what the stack actually means.  Sometimes, just identifying _which_ native module is causing problems is the biggest win.
 
 Cheers, enjoy.  And happy hunting.
 
-# License
+# Contributors
 
-This software is licensed for use under the BSD license. If you make good use of this or any of my other tools, I'd appreciate an email letting me know what you used it for or how you stumbled across it.
+* Dave Dopson (@ddopson): original author and founder of the project
+* Tyler Ang-Wanek (@implausible)
+* Anton Whalley (@No9)
+* Tristan Colgate-McFarlane (@tcolgate)
+* Jan (@relovution)
+* Mikael Korpela (@simison)
+* Benjamin Byholm (@kkoopa)
+* Tim Kevin Oxley (@timoxley)
+* Thomas P (@TPXP)
+* Byron Clark (@byronclark)
+* Mi Tar (@mitar)
+* Rolf Sommerhalder (@hb9cwp)
+* Mark Smith (@markmsmith)
+* Paul-Maxime (@paul-maxime)
+* Kenneth Geisshirt (@kneth): current maintainer
 
-We are using the callstack walker project from [Walking the Callstack](http://www.codeproject.com/Articles/11132/Walking-the-callstack) which is also BSD licensed.
+If you are a contributor and are missing, please create a pull request.
 
-I previously licensed this library under the tounge-in-cheek [WTFPL](http://en.wikipedia.org/wiki/WTFPL), but none of my lawyers thought it was funny.
+# License
 
-   ---  Dave
+This software is licensed for use under the BSD license.
+
+We are using the [callstack walker](https://github.com/JochenKalmbach/StackWalker) project which is also BSD licensed.

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

Misc. License Issues

License

(Experimental) A package's licensing information has fine-grained problems.

Found 1 instance in 1 package

Unidentified License

License

(Experimental) Something that seems like a license was found, but its contents could not be matched with a known license.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

68633

increased by1.79%

Number of low license alerts

0

decreased by-100%

Number of medium license alerts

0

decreased by-100%

License quality

100

increased by25%

Number of lines in readme file

88

increased by20.55%

Worsened metrics

Number of medium supply chain risk alerts

3

increased by50%

No dependency changes