Comparing version 0.0.4 to 1.0.0
{ | ||
"name": "rylaijs", | ||
"description": "spachcock based cliend-side routing thing", | ||
"private": false, | ||
"version": "0.0.4", | ||
"author": "eray <relfishere@gmail.com>", | ||
"version": "1.0.0", | ||
"description": "", | ||
"main": "index.js", | ||
"scripts": { | ||
"build": "browserify src/rylai.js -o build/rylai.js", | ||
"pushState": "node pushState.js" | ||
"test": "echo \"Error: no test specified\" && exit 1" | ||
}, | ||
"dependencies": { | ||
"path-to-regexp": "1.2.1" | ||
}, | ||
"devDependencies": { | ||
"express": "4.13.4" | ||
}, | ||
"keywords": [ | ||
"browser", | ||
"spachcock", | ||
"express", | ||
"route", | ||
"router", | ||
"routing", | ||
"controller", | ||
"library" | ||
], | ||
"repository": { | ||
"type": "git", | ||
"url": "git@github.com:erayarslan/rylai.git" | ||
"url": "git+https://github.com/npm/deprecate-holder.git" | ||
}, | ||
"license": "mit", | ||
"main": "./src/rylai.js" | ||
} | ||
"author": "", | ||
"license": "ISC", | ||
"bugs": { | ||
"url": "https://github.com/npm/deprecate-holder/issues" | ||
}, | ||
"homepage": "https://github.com/npm/deprecate-holder#readme" | ||
} |
@@ -1,23 +0,5 @@ | ||
[![NPM](https://nodei.co/npm/rylaijs.png?downloads=true&downloadRank=true&stars=true)](https://nodei.co/npm/rylaijs/) | ||
# Deprecated Package | ||
## install | ||
This package is no longer supported and has been deprecated. To avoid malicious use, npm is hanging on to the package name. | ||
```sh | ||
$ npm install rylaijs | ||
``` | ||
## build | ||
```sh | ||
$ npm run build | ||
``` | ||
## pushState | ||
```sh | ||
$ npm run pushState | ||
``` | ||
## license | ||
MIT. | ||
Please contact support@npmjs.com if you have questions about this package. |
Possible typosquat attack
Supply chain riskThere is a package with a similar name that is downloaded much more often.
Did you mean |
---|
mitata |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA 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
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
Found 1 instance in 1 package
No tests
QualityPackage does not have any tests. This is a strong signal of a poorly maintained or low quality package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis 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 riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
No website
QualityPackage does not have a website.
Found 1 instance in 1 package
0
0
1
0
669
2
0
6
1
3
- Removedpath-to-regexp@1.2.1
- Removedisarray@0.0.1(transitive)
- Removedpath-to-regexp@1.2.1(transitive)