Package Health Score

42 / 100

security
Security review needed
popularity
Limited
maintenance
Inactive
community
Sustainable

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
2.0.55	\|	07/2018	Popular	0 C 0 H 0 M 0 L	1 H 0 M 0 L
1.10.36	\|	04/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.91	\|	10/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MPL-2.0

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (12)

GitHub Stars: 3
Forks: 0
Contributors: 20

Direct Usage Popularity

The npm package deep-package-manager receives a total of 12 downloads a week. As such, we scored deep-package-manager popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package deep-package-manager, we found that it has been starred 3 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: Yes
Contributors: 20
Funding: No

With more than 10 contributors for the deep-package-manager repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 21
Open PR: 7
Last Release: 6 years ago
Last Commit: 6 years ago

Further analysis of the maintenance status of deep-package-manager based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for deep-package-manager is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=6.0

Age: 9 years
Dependencies: 36 Direct
Versions: 407
Install Size: 884 kB
Dist-tags: 2
# of Files: 309
Maintainers: 1
TS Typings: No

deep-package-manager has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

deep-package-manager

deep-package-manager is the software development tool-chain that abstracts package management and associated development operations. This CLI (aka Command Line Interface) is a Node.js library that works in combination with DEEP Framework.

Getting Started

Step 1. Pre-requisites

[x] Create an Amazon Web Services account
[x] Configure AWS Command Line Interface
[x] Get Started - Installing Git
[x] JDK 8 and JRE 8 Installation Start Here
[x] Install nvm and use node v4.3+
[ ] Install DEEP CLI, also known as deepify:

npm install deepify -g

If you want to use deepify on Windows, please follow the steps from Windows Configuration before running npm install deepify -g and make sure all npm and deepify commands are executed inside Git Bash.

Step 2. Install Microservice(s) Locally

deepify install github://MitocGroup/deep-microservices-helloworld ~/deep-microservices-helloworld

Path parameter in all deepify commands is optional and if not specified, assumes current working directory. Therefore you can skip ~/deep-microservices-helloworld by executing mkdir ~/deep-microservices-helloworld && cd ~/deep-microservices-helloworld before deepify install.

Step 3. Run Microservice(s) in Development

deepify server ~/deep-microservices-helloworld -o

When this step is finished, you can open in your browser the link https://localhost:8000 and enjoy the deep-microservices-helloworld running locally.

Step 4. Deploy Microservice(s) to Production

deepify deploy ~/deep-microservices-helloworld

Amazon CloudFront distribution takes up to 20 minutes to provision, therefore don’t worry if it returns an HTTP error in the first couple of minutes.

Step 5. Remove Microservice(s) from Production

deepify undeploy ~/deep-microservices-helloworld

Amazon CloudFront distribution takes up to 20 minutes to unprovision. That's why deepify command checks every 30 seconds if it's disabled and when successful, removes it from your account.

Developer Resources

Having questions related to deep-package-manager?

Ask questions: https://stackoverflow.com/questions/tagged/deep-framework
Chat with us: https://mitocgroup.slack.com/messages/general
Send an email: feedback@deep.mg

Interested in contributing to deep-package-manager?

Contributing: https://github.com/MitocGroup/deep-package-manager/blob/master/CONTRIBUTING.md
Issue tracker: https://github.com/MitocGroup/deep-package-manager/issues
Releases: https://github.com/MitocGroup/deep-package-manager/releases
Roadmap: https://github.com/MitocGroup/deep-package-manager/blob/master/ROADMAP.md

Looking for web applications that use (or are similar to) deep-package-manager?

Hello World: https://hello.deep.mg | https://github.com/MitocGroup/deep-microservices-helloworld
Todo App: https://todo.deep.mg | https://github.com/MitocGroup/deep-microservices-todomvc
Enterprise Software Marketplace: https://www.deep.mg

deep-package-manager development dependencies

proxyquire

FAQs

What is deep-package-manager?

DEEP Package Manager. Visit Snyk Advisor to see a full health score report for deep-package-manager, including popularity, security, maintenance & community analysis.

Is deep-package-manager popular?

The npm package deep-package-manager receives a total of 12 weekly downloads. As such, deep-package-manager popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is deep-package-manager well maintained?

We found indications that deep-package-manager is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is deep-package-manager safe to use?

While scanning the latest version of deep-package-manager, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 16 November-2024, at 10:47 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP