Package Health Score

53 / 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.10.0	\|	07/2023	Popular	0 C 0 H 0 M 0 L	1 H 0 M 0 L
2.9.0	\|	11/2022		0 C 0 H 0 M 0 L	1 H 0 M 0 L
2.8.0	\|	03/2022		0 C 0 H 0 M 0 L	1 H 0 M 0 L
2.7.0	\|	06/2021		0 C 0 H 0 M 0 L	1 H 0 M 0 L
2.6.0	\|	09/2020		0 C 0 H 0 M 0 L	1 H 0 M 0 L

License

GPL-3.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 (2)

GitHub Stars: 217
Forks: 73
Contributors: 70

Direct Usage Popularity

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

Based on project statistics from the GitHub repository for the npm package pln, we found that it has been starred 217 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: No
Contributors: 70
Funding: No

With more than 10 contributors for the pln repository, this is possibly a sign for a growing and inviting community.

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

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 7
Open PR: 2
Last Release: 1 year ago
Last Commit: 1 year ago

Further analysis of the maintenance status of pln 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 pln 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

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: >= 14.21.1

Age: 6 years
Dependencies: 39 Direct
Versions: 26
Install Size: 37.2 MB
Dist-tags: 1
# of Files: 2.27K
Maintainers: 1
TS Typings: No

pln 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

Pylon IDE

Pylon is a web based integrated development environment built with Node.js as a backend and with a supercharged JavaScript/HTML5 frontend, licensed under GPL version 3. This project originates from Cloud9 v2 project.

About

Pylon is built entirely on a web stack, making it the most hacker-friendly IDE today. Fork it, hack it, make it your own and if you think others would benefit, file a pull request against development branch in this repo or create an issue. You can run Pylon locally or on a remote server - always ready to be available from wherever you are, assisting you to breathe life into every aspect of your ideas and projects.

Features

High performance ACE text editor with bundled syntax highlighting to support a wide range of programming languages.
Modern node support (NodeJS >= 14.21.1)
Up to date dependencies and compatibility fixes
Terminal

Screenshots

Browser used: Safari 12.1.1

Alternative forms based authentication

ScreenShot

The main user interface

ScreenShot

Additional plugin dockpanel view

ScreenShot

Check out pylonide/pylon-plugin-mungit for the Git plugin.

Browser Support

Modern versions of Chrome and Safari are supported. Firefox, altough functional, no longer works as intended as of version 64.0. In the future, efforts will be made to restore compatibility.

Basic iPad Pro support with keyboard

Efforts have been made to make Pylon usable with iPad. However, for a smoother ride, some keyboard settings needs to be changed:

Settings -> General -> Keyboard -> Auto-Correction -> Off
Settings -> General -> Keyboard -> Smart Punctuation -> Off (interferes with coding by changing quotes)
Settings -> General -> Keyboard -> Shortcuts -> Off (interferes by displaying bottom bar that hides the console prompt)

For quality of life it is recommended to remap Caps Lock hardware key to act as an ESC key:

Settings -> General -> Keyboard -> Hardware Keyboard -> Modifier Keys -> Caps Lock Key -> Escape

Installation and Usage

If installing on Windows, please refer to Installation on Windows.

Requirements (>= 2.9.0):

NodeJS >= 14.21.1
g++-4.9 (Required for node-pty compilation)
make (Required for node-pty compilation)
python (Required for node-pty compilation)

Install:

git clone https://github.com/pylonide/pylon.git
cd pylon
npm i

The above install steps creates a pylon directory with a bin/pylon.sh script that can be used to start Pylon:

bin/pylon.sh

Optionally, you may specify the directory you'd like to edit:

bin/pylon.sh -w ~/git/myproject

Pylon will be started as a web server on port -p 3131, you can access it by pointing your browser to: https://localhost:3131

By default Pylon will only listen to localhost. To listen to a different IP or hostname, use the -l HOSTNAME flag. If you want to listen to all IP's:

bin/pylon.sh -l 0.0.0.0

If you are listening to all IPs it is advised to add authentication to the IDE. You can either do this by adding a reverse proxy in front of Pylon, or use the built in basic authentication through the --username and --password flags.

bin/pylon.sh --username leuser --password plnisawesome

Pylon is compatible with all connect authentication layers, to implement your own, please see the plugins-server/cloud9.connect.basic-auth plugin on how we added basic authentication.

Installation on Windows (experimental)

If you are on Windows Insider Program, use the Bash on Windows feature to install Pylon.

Install NVM to manage node versions. Install a node version to your liking. The following is needed to install the needed build tools:

sudo apt-get update
sudo apt-get install build-essential

Clone the Pylon repo to your machine and run npm:

npm install
bin/pylon.sh -w . -l 0.0.0.0

Installation inside Docker container

Pylon IDE can be successfully deployed and run within a container. However, if the npm utility complains permissions during install. One must include --unsafe-perm for the installation to pass successfully.

Updating

To update to the latest version (if this doesn't work, just make a fresh clone):

git pull
npm update

Creating your own Plugins

Pylon functionality is all created around server and client-side plugins. However, there is hardly any documentation about the APIs to create your own plugins. To get you started, please see pylonide/pylon-plugin-mungit to see how to get started for a client-side only plugin.

Going forward, there will be efforts made to sort out the documentation and write some tutorials to make it more easier to get started.

License

The GPL v3.

Contributing

Open new issue for discussion and/or feel free to submit a pull request against the development branch.

pln development dependencies

rimraf @xmldom/xmldom xpath typescript

FAQs

What is pln?

Pylon IDE. Visit Snyk Advisor to see a full health score report for pln, including popularity, security, maintenance & community analysis.

Is pln popular?

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

Is pln well maintained?

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

Is pln safe to use?

While scanning the latest version of pln, 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 1 October-2024, at 00:20 (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

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (2)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

Pylon IDE

About

Features

Screenshots

Alternative forms based authentication

The main user interface

Additional plugin dockpanel view

Browser Support

Basic iPad Pro support with keyboard

Installation and Usage

Installation on Windows (experimental)

Installation inside Docker container

Updating

Creating your own Plugins

License

Contributing

pln dependencies

pln development dependencies

FAQs

What is pln?

Is pln popular?

Is pln well maintained?

Is pln safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues