Helpful links

https://github.com/beta0muerta?tab=stars

https://github.com/atom/atom/releases/tag/v1.59.0

http://coffeescript.org/#linters-and-formatting

https://flight-manual.atom.io/hacking-atom/sections/tools-of-the-trade/

https://chromedevtools.github.io/devtools-protocol/tot/ServiceWorker/

https://developer.chrome.com/blog/new-in-devtools-92/?utm_source=devtools#protocol-monitor

https://developer.chrome.com/docs/

https://github.com/github/roadmap/issues/72

https://docs.github.com/en/enterprise-server@3.3/actions/security-guides/automatic-token-authentication

https://api.github.com/meta

https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation

https://zube.io/docs/components

https://zube.io/ashtree-organic/wordp/tickets/1

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows

https://github.blog/changelog/feed/

https://docs.github.com/en/get-started/learning-about-github/githubs-products

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository

https://docs.github.com/en/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions

https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits

https://docs.github.com/en/actions/using-jobs/using-jobs-in-a-workflow

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

https://opensource.microsoft.com/

Something went wrong. Please refresh the page and/or try again.

!-- BEGIN MICROSOFT SECURITY.MD V0.0.5 BLOCK -->

## Security

Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).

If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.

## Reporting Security Issues

**Please do not report security vulnerabilities through public GitHub issues.**

Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).

If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).

You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc). 

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  * Full paths of source file(s) related to the manifestation of the issue
  * The location of the affected source code (tag/branch/commit or direct URL)
  * Any special configuration required to reproduce the issue
  * Step-by-step instructions to reproduce the issue
  * Proof-of-concept or exploit code (if possible)
  * Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs.

## Preferred Languages

We prefer all communications to be in English.

## Policy

Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).

<!-- END MICROSOFT SECURITY.MD BLOCK -->
Design a site like this with WordPress.com
Get started