Gitiles
Code Review Sign In
gerrit.avm99963.com / infinitegforums / 25ae33615f0cd02dc78109a42f43c94219500656
commit25ae33615f0cd02dc78109a42f43c94219500656[log] [tgz]
authorAdrià Vilanova Martínez <me@avm99963.com>Wed Nov 01 22:26:00 2023 +0100
committerAdrià Vilanova Martínez <me@avm99963.com>Wed Nov 01 22:26:00 2023 +0100
treedf348952282cceae7e35f2bfca72fb49558e70f2
parentf0a026c9a5a8917ffe0ac6b3dc9c1500ae6db8a7 [diff]
build: npm audit fix

Ran the following commands:

```
$ npm audit
\# npm audit report

@babel/traverse  <7.23.2
Severity: critical
Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code - https://github.com/advisories/GHSA-67hx-6x53-jw92
fix available via `npm audit fix`
node_modules/@babel/traverse

postcss  <8.4.31
Severity: moderate
PostCSS line return parsing error - https://github.com/advisories/GHSA-7fh5-64p2-3v2j
fix available via `npm audit fix`
node_modules/postcss

2 vulnerabilities (1 moderate, 1 critical)

To address all issues, run:
  npm audit fix

$ npm audit fix

added 7 packages, changed 16 packages, and audited 641 packages in 6s

60 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
```

Change-Id: I303248790c351991f8ba2d453da136f199859cb7
1 file changed
tree: df348952282cceae7e35f2bfca72fb49558e70f2
  1. .github/
  2. cws/
  3. docs/
  4. playbooks/
  5. roles/
  6. src/
  7. templates/
  8. tools/
  9. .babelrc
  10. .clang-format
  11. .editorconfig
  12. .eslintrc.json
  13. .gitignore
  14. .gitreview
  15. .zuul.yaml
  16. i18n-config.toml
  17. jest.config.js
  18. LICENSE
  19. lit-localize.json
  20. Makefile
  21. OWNERS
  22. package-lock.json
  23. package.json
  24. README.md
  25. tagRelease.bash
  26. webpack.config.js
README.md

TW Power Tools

Available in the Chrome Web Store

Build status Translation status

An extension which brings several enhancements to the Google Forums and the Community Console.

For a list of features/enhancements, check out the feature list doc.

Information for contributors

This extension is being actively developed, and everyone is welcome to make feature requests, report issues and contribute code changes.

In order to make feature requests or report issues, please do so at the Monorail Issue Tracker:

To see a more exhaustive guide on how to contribute, and information on how to contribute code changes, please read the following doc:

Beta channel

Before releasing updates to the stable channel, the newest versions are uploaded to the beta channel so they can be tested by everyone who's interested. This is another way to contribute to the project, because beta testing can make us notice bugs before they reach the stable channel.

The beta channel for Chrome is available here.