Latest Threat Research:SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains.Details →
env-auto - npm Package Compare versions
| # Contributor Covenant Code of Conduct | ||
| ## Our Pledge | ||
| In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. | ||
| ## Our Standards | ||
| Examples of behavior that contributes to creating a positive environment include: | ||
| * Using welcoming and inclusive language | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
| Examples of unacceptable behavior by participants include: | ||
| * The use of sexualized language or imagery and unwelcome sexual attention or advances | ||
| * Trolling, insulting/derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| * Publishing others' private information, such as a physical or electronic address, without explicit permission | ||
| * Other conduct which could reasonably be considered inappropriate in a professional setting | ||
| ## Our Responsibilities | ||
| Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. | ||
| Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. | ||
| ## Scope | ||
| This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. | ||
| ## Enforcement | ||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at github@gatti.pl. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. | ||
| Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. | ||
| ## Attribution | ||
| This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] | ||
| [homepage]: http://contributor-covenant.org | ||
| [version]: http://contributor-covenant.org/version/1/4/ |
| # First off | ||
| Thank you for considering contributing to this project 😀. All my project have one goal, to teach how to write simpler, easier to understand code to the point that a non technical person will understand it. For example: | ||
| - The way I write my comments is on purpose, because I found that this way is the easiest way for a brain to filter out and understand | ||
| - In JavaScript code I just use `let` instead of `const` so no one will get confused, I want people to focus on the article or example, instead of why I used `let` here, and `const` there. | ||
| - On purpose I use as little variables as possible to yet again, not confuse anybody. | ||
| # What I believe in | ||
| - Making everything simpler for everyone to understand. | ||
| - Frameworks force you to be organized, instead of teaching you how to be organized. | ||
| # Childish Code | ||
| A way to say that code should be understood even by a child. Write simple to understand code. Don't make it obscure, and be the only one that can understand it. Be mindful of other people, and their time. |
+1
-1
| { | ||
| "name": "env-auto", | ||
| "version": "1.4.3", | ||
| "version": "1.4.4", | ||
| "description": "convert app.json in to .env", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
+15
-2
@@ -0,1 +1,8 @@ | ||
| [![downloads][downloads-badge]][npm-stat] | ||
| [downloads-badge]: https://img.shields.io/npm/dm/env-auto.svg?style=flat-square | ||
| [npm-stat]: http://npm-stat.com/charts.html?package=env-auto&from=2016-04-01 | ||
| --- | ||
| # 🚗 env-auto | ||
@@ -9,3 +16,3 @@ | ||
| I created this tiny app to automatically generate the `.env` file while making sure the file won't excede the 80 char ruler mark. | ||
| I created this tiny app to automatically generate the `.env` file while making sure the file won't excede the 80 char ruler mark. | ||
@@ -83,4 +90,10 @@ If your `app.json` file has set default values, env-auto will automatically populate the vriables. Anything else will require you to fill in the data. | ||
| If you've enjoyed this article/project, please consider giving it a 🌟. Also check out my [GitHub account](https://github.com/davidgatti), where I have other articles and apps that you might find interesting. | ||
| If you've enjoyed this article/project, please consider giving it a 🌟 or donate. | ||
| - [](https://www.paypal.me/gattidavid/25) | ||
| - [](https://github.com/davidgatti/env-auto/stargazers) | ||
| - [](https://github.com/davidgatti/env-auto/watchers) | ||
| Also check out my [GitHub account](https://github.com/davidgatti), where I have other articles and apps that you might find interesting. | ||
| ## Where to follow | ||
@@ -87,0 +100,0 @@ |
New alerts
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Fixed alerts
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
16667
41.22%- Number of package files
7
40%- Number of lines in readme file
114
12.87%No dependency changes