readme.so
git-secrets
readme.so | git-secrets | |
---|---|---|
34 | 32 | |
3,848 | 12,026 | |
- | 0.6% | |
3.4 | 1.0 | |
about 2 months ago | 22 days ago | |
JavaScript | Shell | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
readme.so
-
Get People Interested in Contributing to Your Open Project
Use the editor at readme.so
-
Created an anime streaming website using react js
Here's the link : https://readme.so/
-
Must-Have Websites for Every Frontend Web Developer
Keep your project's readme organized and attractive with Readme.so. The simple editor allows you to quickly add and customize all the sections you need for your project's readme.
- Must have websites for every Frontend Web developer
-
Check out my first Frontend project named: "Suggest ME A Game"
You should make a better README file (https://readme.so/ can help)
- Proiect nou - documentatie si resurse
-
How to Write an Awesome Readme
readme.so
- Rant si sugestii pentru cei care isi trec GitHub in CV
-
Very help full VS code extension for every programmer
Hay. I just discovered this VS code extension called Readme Editor developed by SumitNalavade. This is much like readme.so but embedded in to VS code, in other words this a README file editor that helps you edit README files for GitHub and is embedded into VS code. There are also lot of templates that you can start your README.md file with. And Once you click the save button your README.md file is automatically saved to your root folder.
-
I built a Readme Editor in VS Code!
After coming cross this feature request, I decided to go ahead and build it myself .
git-secrets
-
Fired for leaked credentials. How do I explain this?
Well, this doesn't really happen at places that don't suck. They had no least privilege access to critical secrets and no processes (like pre-commit hooks using git-secrets) to prevent them being committed.
-
Recovering from Accidentally Pushing Sensitive Information to a Remote Git Repository
# macOS brew install git-secrets # Linux git clone https://github.com/awslabs/git-secrets.git cd git-secrets make install
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
If you pay for an API key depending on the amount of requests, is it safe to push your code to GitHub?
You could use Git hooks to prevent someone from being able to author a commit when you suspect there is a secret being committed. In addition to this, you could also perform this check server-side, in case someone did not run their Git hooks for whatever reason. For example, check out git-secrets.
-
Securing the software supply chain in the cloud
git-secrets
-
How to deal with unintended information leakage when using GitHub as your GIT?
Install git-secrets. Go into each of your repos, scan for past mistakes, and add a git-commit hook:
- GitHub Access Token Exposure
-
Security scanning
I agree that code scanning is really important, the best way to convince others is to identify high-risk threats in source code and present them to the decision-makers. For example, scanning Secrets is great for showing how repositories can be a massive vulnerability and identifying some low-hanging fruit, especially in the git history. Attackers are really after git repository access for this reason and there are plenty of open-source or free tools that you can use to illustrate the problem. Git-Secrets, Truffle Hog. These aren't great for a long-term commercial solution, something like GitGuardian is a better commercial tool but if the goal is just to illustrate the problem then finding some high-value secrets with free tools is a good way to convince the security personnel to invest in some solutions. Then the door is open to having more conversations as you have already proven the risk.
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
I worked for a big startup last year and was on a contract deadline for integrating a vendor framework into a React Native app.
It was taking too long to get a new temp demo license key and GitHub search with clever filters helped me track down a demo key that was recently uploaded to a test repo.
This is also why I use git-secrets in my repos.
https://github.com/awslabs/git-secrets
-
Marking findings as FPs in recurring scans
Under the covers, it is simply looking up an 'ignore' list stored in YML during each scan. If you are building your own, you might also want to see how AWS Labs is doing it in their solution git secrets.
What are some alternatives?
github-profile-readme-generator - 🚀 Generate GitHub profile README easily with the latest add-ons like visitors count, GitHub stats, etc using minimal UI.
trufflehog - Find and verify secrets
Best-README-Template - An awesome README template to jumpstart your projects!
gitleaks - Protect and discover secrets using Gitleaks 🔑
emoji-cheat-sheet - A markdown version emoji cheat sheet
secretlint - Pluggable linting tool to prevent committing credential.
playground-macos - My portfolio website simulating macOS's GUI, developed with React and UnoCSS.
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
commitlint - 📓 Lint commit messages
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
css.gg - 700+ Pure CSS, SVG, PNG & Figma UI Icons Available in SVG Sprite, styled-components, NPM & API and 6000 glyphs
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files