bitcore-message - npm Package Compare versions

Comparing version 1.0.1 to 1.0.2

bower.json

 {
   "name": "bitcore-message",
   "main": "./bitcore-message.min.js",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "homepage": "https://github.com/bitpay/bitcore-message",
@@ -6,0 +6,0 @@ "authors": [

docs/index.md

@@ -1,20 +0,11 @@
----
-title: Message Verification and Signing
-description: Bitcoin Message Verification and Signing.
----
 # Message Verification and Signing
+Bitcore implementation of [bitcoin message signing and verification](http://bitcoin.stackexchange.com/questions/3337/what-are-the-safety-guidelines-for-using-the-sign-message-feature/3339#3339). This is used to cryptographically prove that a certain message was signed by the holder of an address private key.
 
-## Description
-
-Bitcore implementation of [bitcoin message signing and verification]
-(http://bitcoin.stackexchange.com/questions/3337/what-are-the-safety-guidelines-for-using-the-sign-message-feature/3339#3339).
-This is used to cryptographically prove that a certain message was signed by the holder of an address private key.
-
 For more information refer to the [bitcore-message](https://github.com/bitpay/bitcore-message) github repo.
 
 ## Installation
-
 Message Verification and Signing is implemented as a separate module and you must add it to your dependencies:
 
 For node projects:
+
 ```bash
@@ -25,2 +16,3 @@ npm install bitcore-message --save
 For client-side projects:
+
 ```bash
@@ -31,3 +23,2 @@ bower install bitcore-message --save
 ## Example
-
 To sign a message:
@@ -34,0 +25,0 @@

package.json

 {
   "name": "bitcore-message",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Bitcoin Messages for Bitcore",
@@ -29,3 +29,3 @@ "author": "BitPay <[e-mail]>",
   "devDependencies": {
-    "bitcore-build": "bitpay/bitcore-build",
+    "bitcore-build": "braydonf/bitcore-build",
     "brfs": "^1.3.0",
@@ -32,0 +32,0 @@ "chai": "~1.10.0",

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

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

Worsened metrics

Total package byte prevSize

18578

decreased by-0.64%

No dependency changes