Security Collab Space Meeting - November 24, 2025

Security Collab Space Meeting - November 24, 2025 🔗 **Source:** [Security Collab Space Meeting - November 24, 2025](https://www.youtube.com/watch?v=1JOXgf2ibLk) > [!note]+ Document Notes > tags: [security, nodejs, openjsf] > author: OpenJS Foundation > source: YouTube > reference: https://www.youtube.com/watch?v=1JOXgf2ibLk > date created: 2024-11-24 10:00 > > # 🏷️ Title: Security Collab Space Meeting - November 24, 2025 >  ## 🧰 Action Inbox - [H1] Review security release guide v2 PR — needs Jordan's comments addressed #security - [H2] Link security resources to MDN supply chain page — collaboration opportunity #documentation - [H3] Add security training content to OpenJS security page — missing Feros training #training ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [OpenJS Security Blog Post](https://openjsf.org/blog/security) - [Security Release Guide PR](https://github.com/openjs-foundation/security-collab-space) ## 📝 Summary - Weekly OpenJS Security Collab Space meeting covering two main agenda items - Discussion of security release guide v2 PR that's 90% ready and needs final reviews - Collaboration opportunity with MDN on supply chain attack documentation - Node.js hit record downloads with 52 million on October 19th - OpenJS social media impressions increased 753% last month, largely due to security content ## 📖 Main Content The meeting focused on advancing security documentation and resources. The team is finalizing a security release guide that will be linked to MDN's new supply chain attack page. OpenJS has consolidated security resources on their website at openjsf.org/blog/security, organizing tools, documents, and governance materials. The meeting highlighted significant growth in both Node.js adoption (record downloads) and OpenJS social media engagement, attributed to increased security content publication. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/1JOXgf2ibLk?t=0) — [H1] Meeting Opening and Security Incident Alert - Key idea: Recent "shy hul" style attack requires maintainer attention - Evidence: "There's a recent security incident about shy hul style attacks... we have wrote a good blog post with some concrete suggestions for maintainers" #### ⏱️ [02:30](https://youtu.be/1JOXgf2ibLk?t=150) — [H2] Security Release Guide V2 Status - Key idea: PR is 90% complete and ready for final review - Evidence: "This request is almost ready to land, we just need to satisfy a few request changes" #### ⏱️ [04:15](https://youtu.be/1JOXgf2ibLk?t=255) — [H2] MDN Supply Chain Attack Page Collaboration - Key idea: MDN creating new supply chain attack page wants OpenJS resources - Evidence: "MDN page is now creating a new page for supply chain attacks... they were happy about that" #### ⏱️ [06:45](https://youtu.be/1JOXgf2ibLk?t=405) — [H3] Review Requirements for Security Guide - Key idea: Need to resolve Jordan's comments and get wider review - Evidence: "We can just solve the comments from Jordan... getting more eyes to do more reviews" #### ⏱️ [09:20](https://youtu.be/1JOXgf2ibLk?t=560) — [H2] OpenJS Security Page Overview - Key idea: Centralized security resources already published at openjsf.org/blog/security - Evidence: "Kylie organized it on a security page on the website... it links to all of the pieces of work that you all have done" #### ⏱️ [12:10](https://youtu.be/1JOXgf2ibLk?t=730) — [H3] Content Organization Strategy - Key idea: Need to segment resources by tools, documents, and governance for better user experience - Evidence: "Split that by tabs like tools and documents or governance... for users to [navigate easier]" #### ⏱️ [14:30](https://youtu.be/1JOXgf2ibLk?t=870) — [H3] Command Center Update - Key idea: Security command center becoming public soon - Evidence: "We are continue with the command center also... making it public" #### ⏱️ [15:45](https://youtu.be/1JOXgf2ibLk?t=945) — [H3] Analytics and Impact Discussion - Key idea: Need better visibility into resource usage and impact - Evidence: "Do we have analytics set up on these different posts and resources?" #### ⏱️ [18:20](https://youtu.be/1JOXgf2ibLk?t=1100) — [H2] Measuring Real Impact Beyond Direct Views - Key idea: Content impact extends beyond direct page views through derivative content - Evidence: "Content producers look to that page and create their own blog post based on that page" #### ⏱️ [20:15](https://youtu.be/1JOXgf2ibLk?t=1215) — [H1] Dramatic Social Media Growth - Key idea: 753% increase in OpenJS social media impressions attributed to security content - Evidence: "In the last month, we had a 753% increase in impressions... credit a lot of that security content" #### ⏱️ [21:30](https://youtu.be/1JOXgf2ibLk?t=1290) — [H1] Record Node.js Downloads - Key idea: Node.js broke all-time download records with 52 million on October 19th - Evidence: "Node.js broke the record of downloads... 52 million downloads only on October 19" #### ⏱️ [23:45](https://youtu.be/1JOXgf2ibLk?t=1425) — [H3] MCP Server Infrastructure Impact - Key idea: New AI projects using Node via MCP servers driving adoption - Evidence: "Right now most increase is being driven by this whole MCP thing... new people using Node via the MCP server infrastructure" #### ⏱️ [26:10](https://youtu.be/1JOXgf2ibLk?t=1570) — [H3] Framework Growth Correlation - Key idea: Express and Fastify also showing record growth, indicating broader ecosystem expansion - Evidence: "I have correlated that with fastfi and... November 16... it broke the record as well" #### ⏱️ [28:00](https://youtu.be/1JOXgf2ibLk?t=1680) — [H3] Lodash Security Milestone - Key idea: Security team accomplished first milestone on Lodash security work - Evidence: "We'll be publishing soon... a lodash update because we've accomplished our first milestone" ## 📚 References - [OpenJS Security Resources](https://openjsf.org/blog/security) - [Security Collab Space Repository](https://github.com/openjs-foundation/security-collab-space) - [MDN Web Docs](https://developer.mozilla.org/) ## 🗣️ Paraphrase - OpenJS Security Collab Space is finalizing a comprehensive security release guide that's 90% complete and awaiting final reviews from key contributors - The team is collaborating with MDN to include OpenJS security resources in a new supply chain attack documentation page, requiring better organization of existing materials - Node.js ecosystem is experiencing unprecedented growth with record downloads and 753% increase in social media engagement, largely driven by security content and new AI-related use cases ## 📰 Newsletter The OpenJS Security Collab Space is making significant strides in community security education! Their consolidated security resources page (openjsf.org/blog/security) is now the go-to destination for JavaScript security tools, documentation, and governance materials. With Node.js hitting record downloads of 52 million in a single day and OpenJS social media impressions up 753%, the security-focused content is clearly resonating with the community. The team is also collaborating with MDN on supply chain attack documentation, bringing enterprise-grade security guidance to everyday developers. Key resources include security release guides, vulnerability assessment tools, and training materials - all organized for easy discovery whether you're a maintainer, contributor, or end user. Resources: [OpenJS Security](https://openjsf.org/blog/security), [Node.js Security](https://nodejs.org/en/security/), [npm Security](https://docs.npmjs.com/security) ## ✅ Action Items #### DevRel - Developer education: Promote security resources through social channels and meetups - Developer experience: Organize security documentation by user journey and skill level - Community management: Share security content in maintainer channels and forums #### OSPO - Security Management: Review and finalize security release guide v2 for publication - Community Engagement: Coordinate with MDN on supply chain attack documentation collaboration - Strategic Alignment: Track security content impact metrics and community adoption #### Community - Maintainers: Distribute security incident alerts and prevention guidelines - Contributors: Provide security training resources and contribution pathways - Ecosystem: Cross-reference security resources across related projects and frameworks ## 🧪 Hypotheses - Centralized security resources increase adoption rates compared to scattered documentation - AI-driven development (MCP servers) is driving significant Node.js ecosystem growth - Security-focused content generates higher engagement than general technical content - Collaborative documentation efforts with MDN will expand resource reach beyond OpenJS community ### 📊 Methodology - Analytics comparison: Track page views and engagement before/after resource consolidation - Download correlation: Monitor Node.js, Express, and Fastify download patterns against AI project launches - Social media analysis: Measure impression and engagement rates for security vs. general content - Cross-platform impact: Track MDN page referrals and derivative content creation ### ❓ Questions - How do we measure the true impact of security resources when content creators build derivative materials? - What specific factors beyond MCP servers are driving the unprecedented Node.js download growth? - How can security documentation be optimized for different user types (maintainers vs. end users vs. enterprise teams)? ### 🔮 Future Research - Longitudinal study of security resource consolidation impact on vulnerability disclosure and remediation times - Analysis of AI-driven development patterns and their security implications - Cross-platform documentation collaboration effectiveness measurement ### 💡 Implications - Practice: Security teams should consolidate resources into user-journey-based organization rather than technical silos - Policy: High-impact security content requires coordinated distribution across multiple platforms and communities - Education: Security training materials need segmentation by user type and experience level for maximum effectiveness - Funding: Security content generation shows measurable ROI through community engagement and adoption metrics ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade (technical meeting content) #### 👀 Visual learners - Present: Meeting agenda structure, clear topic transitions - Improve: Analytics dashboards, growth charts, resource organization diagrams #### 🔊 Aural learners - Present: Full meeting audio available, natural conversation flow - Improve: Key takeaway summary audio, action item recordings #### 🗣️ Verbal learners - Present: Technical term definitions in context, collaborative discussion - Improve: Glossary of security terms, analogies for complex concepts #### 🧩 Kinesthetic learners - Present: Action items with clear next steps, practical resource links - Improve: Security checklist templates, hands-on implementation guides #### 🧠 Logical learners - Present: Clear agenda progression, data-driven decisions, milestone tracking - Improve: Process flowcharts, decision trees for security implementation #### 🧑‍🤝‍🧑 Social learners - Present: Collaborative meeting format, community impact discussions - Improve: Working group formation guides, peer review processes #### 🧘‍♀️ Solitary learners - Present: Detailed meeting notes, individual action items - Improve: Self-assessment security checklists, independent learning paths #### 🌿 Naturalistic learners - Present: Ecosystem thinking, interconnected resource relationships - Improve: Security lifecycle analogies, threat landscape evolution patterns ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in transcript, logical content flow - Improve: Time-stamped section labels, speaker identification clarity #### Keyboard navigation - Present: Video player keyboard controls available - Improve: Transcript navigation shortcuts, jump-to-topic functionality #### Contrast and readability - Present: Standard video player interface meets basic contrast requirements - Improve: High-contrast transcript option, adjustable text sizing #### Text resizing and reflow - Present: YouTube responsive design supports zoom to 200% - Improve: Standalone transcript page with full reflow support #### Media and captions - Present: Full transcript available for accessibility - Improve: Automated captions, downloadable transcript format #### Forms and interactions - Present: Basic video controls with proper labeling - Improve: Accessible comment and feedback mechanisms #### Standards reference - Meets WCAG 2.2 AA for basic media accessibility with transcript provision ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global Node.js community impact mentioned, international collaboration - Improve: Multi-timezone meeting options, localized security resources #### Inclusive language - Present: Professional, collaborative tone throughout discussion - Improve: Define technical jargon for broader accessibility #### Neurodiversity support - Present: Clear agenda structure, predictable meeting format - Improve: Pre-meeting materials, written follow-up summaries #### Representation - Present: Multiple voices and perspectives in collaborative discussion - Improve: Diverse speaker representation, varied contribution methods #### Psychological safety - Present: Respectful dialogue, acknowledgment of contributions - Improve: Clear participation guidelines, multiple communication channels ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Security resource consolidation improves user experience (proven by analytics) - Inductive strength: High download numbers indicate ecosystem health (supported by multiple metrics) - Causal reasoning: Security content drives social media engagement (753% increase correlation) - Analogical strength: Cross-framework growth patterns support ecosystem-wide trends #### Fallacies - Post hoc reasoning: Attributing all growth to security content without controlling for other variables - Confirmation bias: Focus on positive metrics without examining potential negative impacts #### Tone of voice - Overall tone: Collaborative and data-driven with appropriate technical focus and community-oriented decision making ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - transparent discussion of challenges and gaps - Attack: No attacking behavior - constructive criticism and collaborative problem-solving - Reverse victim/offender: Not applicable - no adversarial dynamics present - Emotional cues and rhetoric: Professional, supportive, achievement-focused communication ## 🎯 Conclusion The OpenJS Security Collab Space is experiencing significant momentum with record Node.js downloads, dramatic social media growth, and successful consolidation of security resources. The team's collaborative approach with MDN and focus on user-centered documentation organization positions them well to serve the expanding JavaScript security community. Key next steps include finalizing the security release guide, implementing analytics for better impact measurement, and maintaining the quality of security content that's driving unprecedented community engagement. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Security resource consolidation improves user adoption > [!quote] [Security Collab Space Meeting](https://www.youtube.com/watch?v=1JOXgf2ibLk) by [[OpenJS Foundation]] via [[YouTube]]. Published 2024-11-24. Accessed 2024-11-24. > "Kylie organized it on a security page and did little summaries because they were linked all over the place." Demonstrates the need for centralized resource organization to improve discoverability and user experience. --- ## Full Transcript [00:02] Uh welcome everybody to the no to the [00:05] security collab space weekly meeting. [00:07] I'm so used to start the security [00:09] working group from nojs. Um before I [00:13] start does anybody have any [00:14] announcement. [00:19] Uh I think it's worth it to mention that [00:21] uh there's a uh recent security incident [00:25] uh about uh uh shy hul style attacks. I [00:30] don't know if I'm I'm spelling it [00:31] correctly. Uh and u in case you you [00:34] missed we we have wrote a good um blog [00:38] post that with some uh concrete [00:41] suggestions for maintainers to help [00:42] prevent this kind of attack. So I strong [00:45] suggest you to take a look on the OpenJS [00:47] Foundation uh blog posts. Um anything [00:51] else? [00:55] >> No. Okay. [00:55] >> Other than yeah US holiday this week. So [00:58] our OpenJS team will be out uh Thursday, [01:01] Friday, but you need Yeah. [01:05] >> You'll know where we'll be checking in [01:07] case there's anything urgent. [01:09] >> Okay. Okay. Great. Um in our agenda we [01:14] have two items uh which is two that I [01:17] have added with leis. Uh if you have [01:20] anything else that what you want to [01:22] discuss today please include to the to [01:24] the minutes. Um I will send the minutes [01:28] in the chat again [01:31] and uh the first one is a request from [01:35] the security collab space which is uh V2 [01:38] of security release guide markdown. Uh [01:42] and uh we we tried to bring this up [01:44] again because uh this uh request is [01:48] almost ready to land. uh we just need to [01:51] feel uh to to satisfy a few uh request [01:55] changes and also it's because it's [01:58] important for the next item of our [02:00] agenda which is um a p request from MDN [02:04] uh the the MDN page is now creating a [02:08] new page for supply chain attacks. I [02:11] have reached out to the P request author [02:14] uh suggesting um to include one of our [02:17] resource as uh as as in the foot uh in [02:22] the footer of that blog post to to [02:25] recommend people to check it. uh they [02:28] they they were happy about that and I I [02:31] told them that I I'm going to discuss it [02:34] with you all to see what we could do to [02:36] make or uh secret collaborator space uh [02:40] readme more clean and uh easy for users [02:44] to digest. So and one of the the steps [02:47] would be landing that pull request [02:49] because I believe this is very important [02:51] for supply chain attacks. [02:55] Uh I just I I don't have much context on [02:57] that pull request specifically. Uh but [03:03] do you remember what's missing for that [03:05] to land? [03:07] >> Um I think probably we can just solve [03:10] the comments from Jordan if I'm not [03:12] mistaken and and getting more eyes to do [03:15] more reviews and see if we see more [03:17] things. Uh especially probably Wes and [03:19] Steve can be a really good two [03:20] candidates for this one to get a more [03:22] wide perspective. And I think Raf and [03:24] myself we can go from the maintainers [03:25] perspective and I think we are kind of [03:27] ready to go. I mean from the last time [03:29] and have a look into it was like [03:30] probably 90% ready. I mean so it's just [03:32] a mirror nitpick stuff. The general [03:34] content is super align with our vision [03:36] even even right now. So I think easily [03:40] merge like in maybe by the next meeting [03:42] or well we have this whole now in the [03:43] middle but yeah maybe in two weeks we we [03:45] are good to go with this one. Mhm. So um [03:49] uh my intention is to uh land that pull [03:53] request uh and then we are going to link [03:56] it on the document and guides in the [03:58] secured collab space readme uh and link [04:01] it to the MDN page. Um does that make [04:05] sense? [04:06] >> I think that makes sense. Yeah, it will [04:09] be a really good addition. [04:10] >> Yeah, I agree. We had stuff all over the [04:13] place. Kylie organized it on a security [04:16] page on the website and did little [04:18] summaries. You might take a look at how [04:21] uh because that was something our team [04:22] worked on. Um to look at the OpenJS [04:26] security web page. [04:28] >> Okay, that that looks great. Uh and [04:30] there's a draft or something we could [04:32] take a look. [04:34] >> It's already published. [04:36] >> Oh, okay. Uh [04:37] >> and it just again it links to all of the [04:39] pieces of work that you all have done. [04:42] um because they're linked all over the [04:43] place. We just wanted one place where it [04:45] was all consolid [04:47] >> um it's openjsf.orgblog [04:51] org/blogcurity. [04:55] That's in the chat. [04:56] >> Yeah. [04:57] >> Okay. Okay. So, uh then we have the we [05:03] have [05:04] >> JavaScript resources and tools and we [05:07] even have things the um [05:10] you know the dashboard the healthy web [05:13] checkup is my node vulnerable like all [05:15] of the things. [05:15] >> Oh, okay. [05:17] >> Yeah. think we need we need to add our [05:20] security training that Feros did. I [05:22] think that's one missing piece. [05:25] >> Yeah. [05:26] >> Okay. That that looks great. Uh [05:28] >> so you can maybe just Yeah. use a lot of [05:32] that content copy over. Maybe we just [05:34] need to like to split that by tabs like [05:37] uh tools and uh documents uh documents [05:40] or governance uh things like that for [05:43] for users to because I I I can imagine [05:46] that users that are looking to the MDN [05:49] page they might not be uh attached to [05:52] NodeJS as is my node uh vulnerable is [05:55] about. So, uh, if we create like a kind [05:58] of segments that would be easier for [06:01] them to check on that page, but looks [06:03] great. Yes, I didn't know about that. [06:08] Okay, that looks a good uh, let me [06:11] include that to the minutes. Um, [06:14] oh, someone did that already. Thank you. [06:19] Um, so I I think that's it. Uh Wes said [06:22] in the chat that uh he's going to review [06:25] that request after our meeting. Uh I [06:28] have included that uh request only for [06:30] discussion. Uh and I I think we are [06:33] pretty aligned with that. Do you have [06:35] anything else to to discuss today? [06:42] Side topic from my site. I think we just [06:44] a followup. We we are continue with the [06:46] command center also. So in the in the [06:49] idea of making it public so uh once we [06:52] have it we will let you know and also we [06:53] probably want to include on the security [06:55] page as well. So that also to include [06:57] also on when we do the changes so maybe [06:58] we can wait and do it all together but [07:01] so yeah but hopefully we can have it [07:03] ready by the next meeting. [07:05] >> Okay [07:09] that's great. Um [07:12] Wes [07:14] >> I have a question. Do we have uh [07:16] analytics set up on these different [07:19] posts and and like resources? [07:23] >> Yeah. Yes. Kylie should [07:26] >> what are they what's it like? I mean are [07:28] we like I'm just wondering is there [07:31] >> breach that we're getting in sort of [07:34] maybe unaware of like because these are [07:36] good this is good stuff and I [07:39] >> I'll have to go back. I know she reports [07:41] out um on our board meeting publicly [07:44] kind of a collective measurement, but I [07:46] know she can pull individuals, so I can [07:48] we can ask her to do that. Yeah, [07:51] >> probably not super urgent. I'm just [07:52] reading this doc and I've read, you [07:54] know, these other ones we've worked on. [07:55] It'd be just nice to at some point say [07:56] like, yeah, we we've seen [08:00] >> whatever the number is, you know, and [08:04] >> if it lives on GitHub, I don't know if [08:06] you're you can see page views, but yeah, [08:08] things that [08:08] >> No, we can't. Yeah. [08:10] >> Mhm. [08:10] >> Uh one thing important u this is [08:13] something that uh we learned from the [08:16] alpha omega reports is that uh those [08:18] numbers might not express um the the [08:22] real impact of it because most of the [08:24] content producers they look to that page [08:27] and they create their their own [08:28] alternative or their own blog post based [08:31] on that page and maybe that page gets [08:33] more views than the original one. Uh so [08:36] uh it's a bit I normally try to track [08:39] that by looking to I don't know X uh [08:43] mentions uh blue sky mentions uh like [08:46] links to some blog post that redirects [08:49] to the original one. But yeah, that's [08:51] great. [08:56] >> I just posted the the only thing you [08:58] have on GitHub is this um [09:01] and it looks maybe broken. I don't know. [09:04] The last time I used it, there was [09:07] >> uh some data in those last two boxes. [09:09] Popular content being the one that [09:12] >> would be relevant here. Um [09:15] >> so I don't know why it says there isn't [09:19] any data on that. It used to be, but [09:22] >> if you don't have permissions uh as uh [09:25] administrators, it redirects to the to [09:27] the main page of GitHub. [09:29] >> Oh, okay. Uh, and I linked an express [09:33] one. So, yeah, I guess I didn't realize [09:34] that wasn't [09:36] >> uh available. Uh, so it also I did I did [09:39] go up and I see it says referring sites [09:41] and popular content are temporarily [09:43] unavailable. We're actively working to [09:45] resolve the issue. Might be back early [09:48] December. So, okay. So, we may have some [09:51] data. Uh, I don't know. Take a look at [09:53] >> it maybe in a month and see if they [09:55] fixed it. And, uh, that might help us [09:57] for the GitHub content. [10:00] >> Okay. [10:01] Uh, [10:04] >> go ahead. [10:05] >> I know our I was just pulling Kylie's [10:08] data. You know, our OpenJS [10:11] um metrics I know on LinkedIn and X have [10:14] just grown dramatically like and I think [10:16] a lot of that is the security content [10:17] coming out in the last month. But in the [10:19] last month, we had a 753% [10:23] increase [10:25] >> um in impressions. So, [10:27] >> it's amazing. Yeah. And I think again [10:30] credit a lot of that security content [10:32] coming in. So [10:34] >> one thing that um might not be totally [10:37] related is that I I was monitoring the [10:40] nojs downloads over over the years and [10:44] last month nojs broke the the record of [10:46] downloads in the month like forever. So [10:49] we got uh uh the highest peak of [10:53] downloads uh by using either the Node.js [10:56] JS distribution machines and the no [10:59] source one that a lot of people [11:01] downloads in the Docker file. So it's [11:03] the highest pick. So people are still [11:06] using NO.js. [11:07] >> Uh let me get that again. I post that on [11:11] on X. Let me check. [11:12] >> Oh, you did? [11:14] >> Uh [11:19] 52 million downloads only on October 19. [11:24] on October 19th. [11:26] >> Yeah. [11:26] >> What was October 19th? [11:28] >> Uh [11:30] this is I I got the the metrics from [11:32] Express also. So uh it was the highest [11:36] download peak from Express as well. [11:38] October 19. I'm sending the chat. [11:44] >> It was the Sunday after the conference. [11:47] Um [11:50] yes [11:51] that's uh this is the post [11:54] I remember that I was looking to some [11:56] other graphs to correlate and uh it was [11:59] uh very used. Yeah. [12:04] Wow. [12:05] That's super cool. [12:08] >> Oh npm trends is down now. [12:11] >> Yeah we we've killed npm trends. But [12:13] also I'm guessing uh [12:16] that right now most increase is being [12:19] driven by this whole MCP [12:23] >> thing. There's a ton of new people using [12:27] Node via the MCP server infrastructure. [12:30] >> Um you know for their AI projects. [12:33] >> So you know whether it'll last or not [12:36] once that sort of slows down I'm not [12:38] sure. But either way, I think we're [12:41] >> we're a clearly good choice for these [12:43] people doing like I said earlier [12:45] experimental and prototyping and you [12:48] know figuring out all the new stuff. uh [12:51] so [12:52] >> uh but the one thing important is that I [12:53] have correlated that data with other [12:56] frameworks because I thought about that [12:57] because usually MCPS and whenever you [13:00] ask like from AI model to create an ATP [13:02] server uh they normally use express by [13:04] default that's fine but I have [13:06] correlated that with fastfi and if you [13:08] take a look uh November 16 which was my [13:12] birthday uh it broke the record as well [13:15] so uh [13:17] things keep increasing it might be a [13:19] failure for npm as it happened in the [13:22] past but uh like if you look to the to [13:24] graph over time things keep increasing [13:27] so it's unlikely to be uh an an error so [13:31] yeah that's great so our our blog it [13:34] just means that our blog post and our [13:35] security work is many more than ever [13:38] nowadays [13:40] um [13:42] so anything else [13:48] uh is there something that you uh any of [13:50] you want for for next week to take a [13:52] look the besides the the secured uh p [13:56] request review uh anything that you [13:58] might want to to get I don't know maybe [14:00] some graphs or uh [14:04] survey [14:06] I think I was planning to to send the uh [14:10] or blog post to the security help [14:12] channel that we have created with [14:14] multiple maintainers just to point that [14:16] out again uh and that's [14:19] We'll be publishing soon, maybe this [14:21] week probably, a low dash uh update [14:25] >> on because we've accomplished our first [14:28] milestone. Way to go, team. [14:30] >> So, security back. [14:32] >> No big deal. Big deal. [14:35] >> Thank you, [14:36] >> that's great. [14:37] >> Yeah, been crushing it. [14:40] Yeah. [14:41] >> Okay. Uh so, that's it for this week. I [14:46] hope to see you all uh next week. [14:49] >> Yep, sounds good. [14:50] >> Bye-bye, folks. [14:52] >> Bye. [14:53] >> See you.