Title: doc: add constraints for mem leak to threat model · nodejs/node@dfb72d1 · GitHub
Open Graph Title: doc: add constraints for mem leak to threat model · nodejs/node@dfb72d1
X Title: doc: add constraints for mem leak to threat model · nodejs/node@dfb72d1
Description: Node.js JavaScript runtime ✨🐢🚀✨. Contribute to nodejs/node development by creating an account on GitHub.
Open Graph Description: As discussed in https://github.com/nodejs-private/node-private/pull/719. We should clarify what the criteria are to accept memory leak as a vulnerability (potential DoS). Signed-off-by: RafaelGSS...
X Description: As discussed in https://github.com/nodejs-private/node-private/pull/719. We should clarify what the criteria are to accept memory leak as a vulnerability (potential DoS). Signed-off-by: RafaelGSS...
Opengraph URL: /nodejs/node/commit/dfb72d158b945a66be6f064e49863786641f6b7c
X: @github
Domain: github.com
| route-pattern | /:user_id/:repository/commit/:name(/*path) |
| route-controller | commit |
| route-action | show |
| fetch-nonce | v2:7583ce72-fc52-6b16-33b2-d048dc5fa0d1 |
| current-catalog-service-hash | f3abb0cc802f3d7b95fc8762b94bdcb13bf39634c40c357301c4aa1d67a256fb |
| request-id | CF04:22F52E:28D1CED:3708EA9:696AE1D3 |
| html-safe-nonce | d224cb66c4ca9ba2a6aab62374ddceaddcb53349c8b7043e7304431b66811243 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDRjA0OjIyRjUyRToyOEQxQ0VEOjM3MDhFQTk6Njk2QUUxRDMiLCJ2aXNpdG9yX2lkIjoiODg2NzgwNzQ1MDEyNzU4OTg0MyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | ac40a13cbebf627c8b2cc0daf13f10f744ca20ee02dec1c1201fdd3c8301b79b |
| hovercard-subject-tag | repository:27193779 |
| github-keyboard-shortcuts | repository,commits,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/nodejs/node/commit/dfb72d158b |
| twitter:image | https://opengraph.githubassets.com/da6ab081a7cde6851d1c7dc832494b38540f2ddd2b7b996aeb077bab7164f917/nodejs/node/commit/dfb72d158b945a66be6f064e49863786641f6b7c |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/da6ab081a7cde6851d1c7dc832494b38540f2ddd2b7b996aeb077bab7164f917/nodejs/node/commit/dfb72d158b945a66be6f064e49863786641f6b7c |
| og:image:alt | As discussed in https://github.com/nodejs-private/node-private/pull/719. We should clarify what the criteria are to accept memory leak as a vulnerability (potential DoS). Signed-off-by: RafaelGSS... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:updated_time | 1753486324 |
| hostname | github.com |
| expected-hostname | github.com |
| None | 5f99f7c1d70f01da5b93e5ca90303359738944d8ab470e396496262c66e60b8d |
| turbo-cache-control | no-cache |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 3d84d50b3c75fa36755c3cf392edbc09e626f979 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width