airship - npm Package Compare versions

Comparing version 0.1.0 to 0.1.1

History.md

@@ -0,3 +1,7 @@
+# 0.1.1
+
+* More liberal Node requirement in package.json
+
 # 0.1.0
 
 * Initial release

lib/index.js

@@ -14,2 +14,2 @@ var Airship = require('./airship').Airship;
 
-exports.version = '0.1.0';
+exports.version = '0.1.1';

package.json

@@ -5,3 +5,3 @@ {
   "author": "James F. Herdman <[e-mail]>",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "keywords": ["urban airship", "api", "push messages", "airship"],
@@ -16,3 +16,3 @@ "repository": {
   "engines": {
-    "node": "~0.6.10"
+    "node": "~0.6.3"
   },
@@ -22,11 +22,11 @@ "dependencies": {
   "devDependencies": {
-    "mocha": "~0.12.0",
-    "should": "~0.5.1",
-    "nock": "git://github.com/jherdman/nock.git#issue-41"
+    "mocha": "~1.0.0",
+    "should": "~0.6.0",
+    "nock": "~0.11.2"
   },
   "main": "index",
   "scripts": {
-    "prepublish": "npm prune",
+    "prepublish": "npm prune && ./scripts/prepublish.js",
     "test": "make spec"
   }
 }

README.md

 # airship [![Build Status](https://secure.travis-ci.org/jherdman/airship.png)](http://travis-ci.org/jherdman/airship)
 
-A wrapper for the Urban Airship API. It's largely an experiment of mine to learn more about event-based programming in Node.js.
+A wrapper for the [Urban Airship](http://urbanairship.com) API. It's largely an experiment of mine to learn more about event-based programming in Node.js.
 
-# Usage
+## Usage
 
 Please see examples in the `integration` directory for usage. Given that this is such an early release, I'm very open to suggestion on how to evolve the API of this library.
 
-# License
+## Resources
 
-## MIT License
+* [Urban Airship](http://urbanairship.com)
+* [Urban Airship documentation](http://urbanairship.com/docs/)
 
+## License
+
+### MIT License
+
 Copyright (c) 2012 James F. Herdman
@@ -14,0 +19,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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

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

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

Improved metrics

Total package byte prevSize

16779

increased by3.54%

Number of package files

14

increased by7.69%

Lines of code

365

increased by3.11%

Number of lines in readme file

25

increased by25%

Worsened metrics

Number of low supply chain risk alerts

2

increased byInfinity%

No dependency changes