Package Health Score

36 / 100

security
Security review needed
popularity
Limited
maintenance
Inactive
community
Limited

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
1.3.0	\|	04/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.2.2	\|	03/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.2	\|	01/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.3	\|	01/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.2	\|	12/2013		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

No

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 (2)

GitHub Stars: 9
Forks: 2
Contributors: 1

Direct Usage Popularity

The npm package appup receives a total of 2 downloads a week. As such, we scored appup popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package appup, we found that it has been starred 9 times.

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

Community

Limited

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

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like appup is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 0
Open PR: 0
Last Release: 11 years ago
Last Commit: 11 years ago

Further analysis of the maintenance status of appup 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 appup 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: not defined

Age: 11 years
Dependencies: 11 Direct
Versions: 25
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 1
TS Typings: No

appup 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

appup

CLI to launch apps that use an express main server and an optional restif api server.

Servers are super stable with the help of domains and the cluster module. This means in practice that when a request causes an unhandled error a 500 response is sent, the server shut down gracefully and a new one spun up.

Two servers are spun up originally for each port, so that while one is restarted, the other one keeps servicing incoming requests.

Installation

npm install appup

CLI

appup [options] file

Options:
  --pages      port to start pages server on
  --watchdir   directory to watch for client side JavaScript changes in order to automatically refresh
  --dedupe     if set it will [dynamically dedupe] (https://github.com/thlorenz/dynamic-dedupe)
	             all modules as they are being required to work around the fact that symlinks break `npm dedupe`
  --api        port to start api server on
  --apihost    address at which api server is hosted [default: "localhost"]
  --tunnel     sets up local tunnel pointing to pages port and logs url to connect to from remote client
  --config     point to a config file to override routes, etc. for the pages and api server
  --nocluster  if set, single servers are launched instead of a cluster of them, which maybe preferred during development

API

appup(opts)

Creates browserify bundle and starts up pages server and/or api server according to the supplied options.

If no api port is given, the api server is not started up. If no pages port is given, the pages server is not started up. If neither port is given, an error is thrown.

Parameters:

Name Type Description

opts

Object

Properties

Name	Type	Argument	Description
`pagesPort`	number	<optional>	port at which to start up pages server
`apiPort`	number	<optional>	port at which to start up api server
`apiHost`	string	<optional>	specifies where api server is hosted (default: 'localhost')
`config`	string		full path configuration provided to override browserify specific options and/or custom API/Pages servers init functions
`entry`	string		entry file to add to browserify
`watchdir`	string	<optional>	turns on live reload for the given directory
`dedupe`	boolean	<optional>	turns on dynamic-dedupe
`tunnel`	boolean	<optional>	sets up local tunnel pointing to @see opts.pagesPort and logs url to connect to from remote client
`nocluster`	boolean	<optional>	(default: `false`) if set to `true` single servers are launched instead of a cluster of them

Source:

index.js, line 65

generated with docme

config

The config needs to provide either or all of the following properties on the module exports object:

bundleOpts: {Object} options passed to browserify().bundle(options)
initBrowserify: {Function} invoked with browserify that needs to return a browserify instance that can be initialized according to our needs
initPages {Function} invoked with (pagesApp, express, apiServerInfo) where apiServerInfo is { host: {string}, port: {number} }
postInitPages {Function} invoked with (pagesApp, pagesServer, express) where pagesServer is the result of pagesApp.listen()
pagesSend500 {Function} invoked with (req, res, err) to allow responding with a 500 error before worker gets taken offline and another one is launched
initApi {Function} invoked with (apiApp, restify)
postInitApi {Function} invoked with (apiApp, apiServer, restify) where apiServer is the result of apiApp.listen()
apiSend500 {Function} invoked with (req, res, err) to allow responding with a 500 error before worker gets taken offline and another one is launched
events {EventEmitter} used to emit info and error events, if not provided messages are logged to the console instead

Example config

// Bundle options
exports.bundleOpts = { debug: true, insertGlobals: false };

exports.initBrowserify = function (browserify) {
  return browserify().transform('hbsfy');
};

// Server options

// Pages
exports.initPages = function (pagesApp, express, apiServerInfo) {
  pagesApp.use(core.renderViewMiddleware(viewPath, { title: 'core' }));
};

exports.postInitPages = function (pagesApp, pagesServer, express) {
};

// API 
exports.initApi = function (apiApp, restify) {
};

exports.postInitApi = function (apiApp, apiServer, restify) {
};

License

MIT

appup dependencies

express restify optimist dynamic-dedupe cheerio sse-stream watchr browserify cuid xtend localtunnel

appup development dependencies

FAQs

What is appup?

CLI to launch apps that use an express main server and an optional restif api server. Visit Snyk Advisor to see a full health score report for appup, including popularity, security, maintenance & community analysis.

Is appup popular?

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

Is appup well maintained?

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

Is appup safe to use?

While scanning the latest version of appup, 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 13 November-2024, at 12:21 (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

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

Monitor for new issues

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