home.social

#lodash — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lodash, aggregated by home.social.

  1. Ulises Gascon @ulisesgascon ·

    🔖 The latest issue of my is live, issue 013.

    March recap: 12 CVEs across , , & , a state-actor supply chain attack on , and the security bug bounty paused 🔐

    blog.ulisesgascon.com/newslett

    #newsletter #undici #fastify #lodash #pathtoregexp #axios
  2. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is live, issue 013.

    March recap: 12 CVEs across #undici, #Fastify, #Lodash & #pathtoregexp, a state-actor supply chain attack on #axios, and the #Nodejs security bug bounty paused 🔐

    blog.ulisesgascon.com/newslett

    #newsletter #undici #fastify #lodash #pathtoregexp #axios
  3. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is live, issue 013.

    March recap: 12 CVEs across #undici, #Fastify, #Lodash & #pathtoregexp, a state-actor supply chain attack on #axios, and the #Nodejs security bug bounty paused 🔐

    blog.ulisesgascon.com/newslett

    #nodejs #axios #pathtoregexp #lodash #fastify #undici
  4. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is live, issue 013.

    March recap: 12 CVEs across #undici, #Fastify, #Lodash & #pathtoregexp, a state-actor supply chain attack on #axios, and the #Nodejs security bug bounty paused 🔐

    blog.ulisesgascon.com/newslett

    #newsletter #undici #fastify #lodash #pathtoregexp #axios
  5. Ulises Gascon @ulisesgascon ·

    🔐 7 out of 10 of reports for and are invalid.

    The current spike is LLM-generated noise eating volunteers' time that should go to releases, features, and real bugs.

    Our tooling wasn't designed for this volume. Every report still needs to be read, cross-referenced, and responded to. We need better tooling and support to sustain this.

    #security #lodash #express
  6. Ulises Gascon @[email protected] ·

    🔐 7 out of 10 of #security reports for #Lodash and #Express are invalid.

    The current spike is LLM-generated noise eating volunteers' time that should go to releases, features, and real bugs.

    Our tooling wasn't designed for this volume. Every report still needs to be read, cross-referenced, and responded to. We need better tooling and support to sustain this.

    #security #lodash #express
  7. Ulises Gascon @[email protected] ·

    🔐 7 out of 10 of #security reports for #Lodash and #Express are invalid.

    The current spike is LLM-generated noise eating volunteers' time that should go to releases, features, and real bugs.

    Our tooling wasn't designed for this volume. Every report still needs to be read, cross-referenced, and responded to. We need better tooling and support to sustain this.

    #security #lodash #express
  8. Ulises Gascon @[email protected] ·

    🔐 7 out of 10 of #security reports for #Lodash and #Express are invalid.

    The current spike is LLM-generated noise eating volunteers' time that should go to releases, features, and real bugs.

    Our tooling wasn't designed for this volume. Every report still needs to be read, cross-referenced, and responded to. We need better tooling and support to sustain this.

    #express #lodash #security
  9. Ulises Gascon @[email protected] ·

    🔐 7 out of 10 of #security reports for #Lodash and #Express are invalid.

    The current spike is LLM-generated noise eating volunteers' time that should go to releases, features, and real bugs.

    Our tooling wasn't designed for this volume. Every report still needs to be read, cross-referenced, and responded to. We need better tooling and support to sustain this.

    #security #lodash #express
  10. Ulises Gascon @ulisesgascon ·

    🔖 The latest issue of my is live, issue 011.

    Secure publishing on in 2026, major security overhaul, updated security best practices, fresh release backlog & ecosystem insights from talks, CVEs & community work ✨

    blog.ulisesgascon.com/newslett

    #newsletter #npm #lodash #express
  11. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is live, issue 011.

    Secure publishing on #npm in 2026, major #Lodash security overhaul, updated security best practices, fresh #Express release backlog & ecosystem insights from talks, CVEs & community work ✨

    blog.ulisesgascon.com/newslett

    #newsletter #npm #lodash #express
  12. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is live, issue 011.

    Secure publishing on #npm in 2026, major #Lodash security overhaul, updated security best practices, fresh #Express release backlog & ecosystem insights from talks, CVEs & community work ✨

    blog.ulisesgascon.com/newslett

    #express #lodash #npm #newsletter
  13. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is live, issue 011.

    Secure publishing on #npm in 2026, major #Lodash security overhaul, updated security best practices, fresh #Express release backlog & ecosystem insights from talks, CVEs & community work ✨

    blog.ulisesgascon.com/newslett

    #newsletter #npm #lodash #express
  14. Ulises Gascon @ulisesgascon ·

    Just shipped a new newsletter to Sponsors! 🎁

    Includes the hard truths of security, updates, and the overhaul that put my code in space 🚀.

    Get early access & support my OSS work here: github.com/sponsors/UlisesGasc

    #npm #expressjs #lodash
  15. Ulises Gascon @[email protected] ·

    Just shipped a new newsletter to Sponsors! 🎁

    Includes the hard truths of #npm security, #Expressjs updates, and the #Lodash overhaul that put my code in space 🚀.

    Get early access & support my OSS work here: github.com/sponsors/UlisesGasc

    #npm #expressjs #lodash
  16. Ulises Gascon @[email protected] ·

    Just shipped a new newsletter to Sponsors! 🎁

    Includes the hard truths of #npm security, #Expressjs updates, and the #Lodash overhaul that put my code in space 🚀.

    Get early access & support my OSS work here: github.com/sponsors/UlisesGasc

    #lodash #expressjs #npm
  17. Ulises Gascon @[email protected] ·

    Just shipped a new newsletter to Sponsors! 🎁

    Includes the hard truths of #npm security, #Expressjs updates, and the #Lodash overhaul that put my code in space 🚀.

    Get early access & support my OSS work here: github.com/sponsors/UlisesGasc

    #npm #expressjs #lodash
  18. Ulises Gascon @ulisesgascon ·

    🛠️ Análisis en profundidad del parche de para CVE-2025-13465 en : causa raíz, mecánica de prototype pollution en _.unset/_.omit y detalles del parche.

    orbitant.com/prototype-polluti

    #seguridad #lodash
  19. Ulises Gascon @[email protected] ·

    🛠️ Análisis en profundidad del parche de #seguridad para CVE-2025-13465 en #Lodash: causa raíz, mecánica de prototype pollution en _.unset/_.omit y detalles del parche.

    orbitant.com/prototype-polluti

    #seguridad #lodash
  20. Ulises Gascon @[email protected] ·

    🛠️ Análisis en profundidad del parche de #seguridad para CVE-2025-13465 en #Lodash: causa raíz, mecánica de prototype pollution en _.unset/_.omit y detalles del parche.

    orbitant.com/prototype-polluti

    #lodash #seguridad
  21. Ulises Gascon @[email protected] ·

    🛠️ Análisis en profundidad del parche de #seguridad para CVE-2025-13465 en #Lodash: causa raíz, mecánica de prototype pollution en _.unset/_.omit y detalles del parche.

    orbitant.com/prototype-polluti

    #seguridad #lodash
  22. Ulises Gascon @ulisesgascon ·

    🛠️ In-depth breakdown of the fix for CVE-2025-13465 in : root cause, prototype pollution mechanics in _.unset/_.omit, and details of the patch.

    orbitant.com/en/prototype-poll

    #security #lodash
  23. Ulises Gascon @[email protected] ·

    🛠️ In-depth breakdown of the #security fix for CVE-2025-13465 in #Lodash: root cause, prototype pollution mechanics in _.unset/_.omit, and details of the patch.

    orbitant.com/en/prototype-poll

    #security #lodash
  24. Ulises Gascon @[email protected] ·

    🛠️ In-depth breakdown of the #security fix for CVE-2025-13465 in #Lodash: root cause, prototype pollution mechanics in _.unset/_.omit, and details of the patch.

    orbitant.com/en/prototype-poll

    #lodash #security
  25. Ulises Gascon @[email protected] ·

    🛠️ In-depth breakdown of the #security fix for CVE-2025-13465 in #Lodash: root cause, prototype pollution mechanics in _.unset/_.omit, and details of the patch.

    orbitant.com/en/prototype-poll

    #security #lodash
  26. Ulises Gascon @ulisesgascon ·

    🥹 Proud to have contributed to the security overhaul. Strengthening governance, security processes, and infrastructure to keep the project healthy for the community 🛡️

    openjsf.org/blog/lodash-securi

    #lodash
  27. Ulises Gascon @[email protected] ·

    🥹 Proud to have contributed to the #Lodash security overhaul. Strengthening governance, security processes, and infrastructure to keep the project healthy for the community 🛡️

    openjsf.org/blog/lodash-securi

    #lodash
  28. Ulises Gascon @[email protected] ·

    🥹 Proud to have contributed to the #Lodash security overhaul. Strengthening governance, security processes, and infrastructure to keep the project healthy for the community 🛡️

    openjsf.org/blog/lodash-securi

    #lodash
  29. Ulises Gascon @[email protected] ·

    🥹 Proud to have contributed to the #Lodash security overhaul. Strengthening governance, security processes, and infrastructure to keep the project healthy for the community 🛡️

    openjsf.org/blog/lodash-securi

    #lodash
  30. Ulises Gascon @ulisesgascon ·

    Big news 🚀! is now on Open Collective!

    Support the project and be among the first backers or sponsors 🙌

    opencollective.com/lodash

    #lodash
  31. Ulises Gascon @[email protected] ·

    Big news 🚀! #Lodash is now on Open Collective!

    Support the project and be among the first backers or sponsors 🙌

    opencollective.com/lodash

    #lodash
  32. Ulises Gascon @[email protected] ·

    Big news 🚀! #Lodash is now on Open Collective!

    Support the project and be among the first backers or sponsors 🙌

    opencollective.com/lodash

    #lodash
  33. Ulises Gascon @[email protected] ·

    Big news 🚀! #Lodash is now on Open Collective!

    Support the project and be among the first backers or sponsors 🙌

    opencollective.com/lodash

    #lodash
  34. Ulises Gascon @[email protected] ·

    Big news 🚀! #Lodash is now on Open Collective!

    Support the project and be among the first backers or sponsors 🙌

    opencollective.com/lodash

    #lodash
  35. Ulises Gascon @ulisesgascon ·

    🔖 The latest issue of my is out, issue 010.

    Stories from reviving & reimagining , secure publishing on , why doesn’t fail because of code, backlog updates & ✨

    blog.ulisesgascon.com/newslett

    #newsletter #expressjs #lodash #npm #oss #openssf
  36. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is out, issue 010.

    Stories from reviving #Expressjs & reimagining #Lodash, secure publishing on #npm, why #OSS doesn’t fail because of code, backlog updates & #OpenSSF #Scorecard ✨

    blog.ulisesgascon.com/newslett

    #newsletter #expressjs #lodash #npm #oss #openssf
  37. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is out, issue 010.

    Stories from reviving #Expressjs & reimagining #Lodash, secure publishing on #npm, why #OSS doesn’t fail because of code, backlog updates & #OpenSSF #Scorecard ✨

    blog.ulisesgascon.com/newslett

    #scorecard #openssf #oss #npm #lodash #expressjs
  38. Ulises Gascon @[email protected] ·

    🔖 The latest issue of my #newsletter is out, issue 010.

    Stories from reviving #Expressjs & reimagining #Lodash, secure publishing on #npm, why #OSS doesn’t fail because of code, backlog updates & #OpenSSF #Scorecard ✨

    blog.ulisesgascon.com/newslett

    #newsletter #expressjs #lodash #npm #oss #openssf
  39. Ulises Gascon @ulisesgascon ·

    ✍️ El open source no falla por el código.
    Falla por problemas de gobernanza, burnout y trabajo invisible.

    He escrito sobre lo que aprendí trabajando en y :

    blog.ulisesgascon.com/el-open-

    #expressjs #lodash
  40. Ulises Gascon @[email protected] ·

    ✍️ El open source no falla por el código.
    Falla por problemas de gobernanza, burnout y trabajo invisible.

    He escrito sobre lo que aprendí trabajando en #Expressjs y #Lodash:

    blog.ulisesgascon.com/el-open-

    #expressjs #lodash
  41. Ulises Gascon @[email protected] ·

    ✍️ El open source no falla por el código.
    Falla por problemas de gobernanza, burnout y trabajo invisible.

    He escrito sobre lo que aprendí trabajando en #Expressjs y #Lodash:

    blog.ulisesgascon.com/el-open-

    #lodash #expressjs
  42. Ulises Gascon @[email protected] ·

    ✍️ El open source no falla por el código.
    Falla por problemas de gobernanza, burnout y trabajo invisible.

    He escrito sobre lo que aprendí trabajando en #Expressjs y #Lodash:

    blog.ulisesgascon.com/el-open-

    #expressjs #lodash
  43. Ulises Gascon @ulisesgascon ·

    ✍️ Open source doesn’t fail because of code.
    It fails because of governance gaps, burnout, and invisible work.

    I wrote down what I learned working on and

    blog.ulisesgascon.com/open-sou

    #expressjs #lodash
  44. Ulises Gascon @[email protected] ·

    ✍️ Open source doesn’t fail because of code.
    It fails because of governance gaps, burnout, and invisible work.

    I wrote down what I learned working on #Expressjs and #Lodash

    blog.ulisesgascon.com/open-sou

    #expressjs #lodash
  45. Ulises Gascon @[email protected] ·

    ✍️ Open source doesn’t fail because of code.
    It fails because of governance gaps, burnout, and invisible work.

    I wrote down what I learned working on #Expressjs and #Lodash

    blog.ulisesgascon.com/open-sou

    #lodash #expressjs
  46. Ulises Gascon @[email protected] ·

    ✍️ Open source doesn’t fail because of code.
    It fails because of governance gaps, burnout, and invisible work.

    I wrote down what I learned working on #Expressjs and #Lodash

    blog.ulisesgascon.com/open-sou

    #expressjs #lodash
  47. Ulises Gascon @ulisesgascon ·

    📺 ¿Qué viene después del caos?

    Lecciones de revivir y reimaginar .

    youtube.com/watch?v=NHsIxEy0_Qw

    #expressjs #lodash
  48. Ulises Gascon @[email protected] ·

    📺 ¿Qué viene después del caos?

    Lecciones de revivir #Expressjs y reimaginar #Lodash.

    youtube.com/watch?v=NHsIxEy0_Qw

    #expressjs #lodash
  49. Ulises Gascon @[email protected] ·

    📺 ¿Qué viene después del caos?

    Lecciones de revivir #Expressjs y reimaginar #Lodash.

    youtube.com/watch?v=NHsIxEy0_Qw

    #lodash #expressjs
  50. Ulises Gascon @[email protected] ·

    📺 ¿Qué viene después del caos?

    Lecciones de revivir #Expressjs y reimaginar #Lodash.

    youtube.com/watch?v=NHsIxEy0_Qw

    #expressjs #lodash