[cpesuggest] Add CPE prefix for third_party/android_deps/autorolled/committed/libs/io_grpc_grpc_binder/README.chromium.

To verify the correctness of the suggested CPE Prefix, please follow the
steps below:
1. Visit the National Vulnerability Database (NVD) page for the suggested
   CPE Prefix here: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.2&keyword=cpe:/a:grpc:grpc&status=FINAL%2CDEPRECATED
2. Check whether the third-party dependency for which the CPE Prefix is
   suggested matches the project listed in the NVD page.
3. If the open source project matches and the CPE prefix is not deprecated,
   please Code-Review+1 and submit if you have enough votes.
4. If the open source project does not match or if the CPE prefix is
   deprecated, please add the incorrect suggestion to go/ignored_cpes_textproto
   and add the reason why the suggestion is incorrect.

Adding CPE prefixes to a README.chromium file is recommended practice [1] to
enable automated vulnerability monitoring. For more information on how CPE
prefixes are used see the Chromium Third Party docs [2].

[1] https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/README.chromium.template

[2] https://chromium.googlesource.com/chromium/src/+/HEAD/docs/adding_to_third_party.md#add-a-readme_chromium

Bug: b/290294330
Change-Id: I8e80e3312ec1e730cf492e0e57ea5b2fb2601eb5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779371
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Joey Scarr <jsca@google.com>
Auto-Submit: CPE Updater <chops-security-cronjobs-cpesuggest@prod.google.com>
Commit-Queue: Joey Scarr <jsca@google.com>
Cr-Commit-Position: refs/heads/main@{#1491736}
1 file changed
tree: 8a6b80643325409988cb4affa37398c346b26e42
  1. .github/
  2. agents/
  3. android_webview/
  4. apps/
  5. ash/
  6. base/
  7. build/
  8. build_overrides/
  9. buildtools/
  10. cc/
  11. chrome/
  12. chromecast/
  13. chromeos/
  14. codelabs/
  15. components/
  16. content/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia_web/
  23. gin/
  24. google_apis/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. net/
  33. pdf/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .cursorignore
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.