@availity/authorize
Advanced tools
Comparing version 1.3.1 to 1.3.2-alpha.139
{ | ||
"name": "@availity/authorize", | ||
"version": "1.3.1", | ||
"version": "1.3.2-alpha.139+2035e30d", | ||
"author": "Evan Sharp <evan.sharp@gmail.com>", | ||
@@ -38,3 +38,3 @@ "description": "Check user permissions to see if the current user is authorized to see your content.", | ||
}, | ||
"gitHead": "ff47c71236caaa25df52b38225fdd4a224b45474" | ||
"gitHead": "2035e30decfb44830e58ea81576e08d23d04ea5e" | ||
} |
Manifest confusion
Supply chain riskThis package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.
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 v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
21151
2
2