CheatSheetSeries
semver
CheatSheetSeries | semver | |
---|---|---|
49 | 727 | |
26,660 | 7,044 | |
1.4% | 0.9% | |
9.2 | 0.6 | |
5 days ago | 24 days ago | |
Python | ||
Creative Commons Attribution Share Alike 4.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.
CheatSheetSeries
-
Next.js: consequence of AppRouter on your CSP
Cross Site Scripting Prevention Cheat Sheet from OWASP Cheat Sheet Series
-
A guide to Auth & Access Control in web apps π
OWasp cheat sheet on how to do ACL in Web App.
- Ask HN: Best Practices Guides You're Aware Of
-
Advice For Securing Backend Code
I recommend reading OWASP cheat sheets , especially these:
- What are some senior level learning resources you recommend for improving as a backend engineer?
-
OWASP Attacks spreadsheet?
If it's anywhere it's probably in here, https://cheatsheetseries.owasp.org/
- How do you all SECURE your Apps?
-
What is the easiest and most secure way to implement security in a NestJS application?
Im noob but i read somewhere that if u just follow this https://cheatsheetseries.owasp.org/ Your website is secured
-
OWASP Needs to Evolve
Fixed: https://github.com/OWASP/CheatSheetSeries/issues/1089#issuec...
-
When to implement a back end for a web application?
The most helpful "convention" for building a web application is the OWASP CheatSheet Series that focuses on security best practices.
semver
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseβ¦
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
What are some alternatives?
WhatWeb - Next generation web scanner
react-native - A framework for building native applications using React
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
semantic-release - :package::rocket: Fully automated version management and package publishing
dirsearch - Web path scanner
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
big-list-of-naughty-strings - The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
docker-socket-proxy - Proxy over your Docker socket to restrict which requests it accepts
helmfile - Deploy Kubernetes Helm Charts
django-mfa2 - A Django app that handles MFA, it supports TOTP, U2F, FIDO2 U2F (Webauthn), Email Token and Trusted Devices
Poetry - Python packaging and dependency management made easy