Back to @openjsf's profile

OpenJS Foundation engagement report

@openjsf - 318K followers on X

Measured over 5 original posts from a 30-day window, last computed on October 14, 2026.

Engagement

Per follower
0.004%
of 318K followers
Per impression
0.355%
3.7K views on a typical post
Reach
1.15%
of its followers see a post
Typical post
13
interactions (median)
Saved
0.027%
1 bookmarks on a typical post
Posting rate
0.27/day
active 23% of days
Peak time
13:00 UTC
Tuesday

Early reading. We have captured 5 original posts for this account, below the 8 we require before treating a median as settled. The numbers above describe what we have seen so far, not a finished profile of the account.

A typical post picks up 13 interactions against 318K followers, an engagement rate of 0.004%. Posts are seen about 3.7K times each, and 0.355% of those impressions turn into an interaction. That is about 1.15% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.27 posts a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 13:00 UTC, and Tuesday is the busiest day of the week. Of the 5 posts sampled, 40% carry an image or video and 100% link out. The account's strongest tracked post pulled 125 interactions, about 9.6x its own typical post. Recurring topics include #nodejs, #opensource. Only 5 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.

Measured over 5 original posts from a 30-day window, last computed on October 14, 2026. Recurring tags: #nodejs, #opensource.

Where this sits in the catalog

At 0.004%, OpenJS Foundation sits above the 10th percentile of the 204,424 accounts in this comparison. That places it in the bottom 25% band, which runs below 0.024%.

p100.004%
p250.024%
p50 (median)0.143%
p750.677%
p902.55%
p9982.4%
Engagement rate as a share of followers, across the 204,424 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 22,888 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.004%
25th percentile0.024%
50th percentile0.143%
75th percentile0.677%
90th percentile2.55%
99th percentile82.4%

This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built

Posting timing

This account posts most often around 13:00 UTC, and Tuesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 13:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 13:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
00:00 UTC-1%89K
01:00 UTC-2%90K
02:00 UTC-3%88K
03:00 UTC-4%94K
04:00 UTC-5%76K
05:00 UTC-4%75K
06:00 UTC-5%86K
07:00 UTC-5%93K
08:00 UTC-4%108K
09:00 UTC-4%124K
10:00 UTC-3%129K
11:00 UTC-3%141K
12:00 UTC-3%154K
13:00 UTC-3%167K
14:00 UTC-4%173K
15:00 UTC-2%176K
16:00 UTC-3%171K
17:00 UTC-3%159K
18:00 UTC-2%149K
19:00 UTC-2%141K
20:00 UTC-1%131K
21:00 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Tuesday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Tuesday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

Formats this account uses

Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video40% of posts+111%+108% to +115%34K
Outbound link100% of posts-41%-42% to -40%32K
Typical length-+15%+14% to +16%32K
  • 40% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
  • 100% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
  • Its average post runs 364 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above the same accounts' other posts.

These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.

Best tweets

  • May 5, 20269.6x their median

    Maintainer Month is here, with better tools, helpful resources, and community events for the people behind the code. 💻 Check out what’s new. 👇 https://t.co/CvPO32H7d8

    95179430K viewsView on X
  • Aug 28, 20267.2x their median

    NativeScript 9.1 adds Node-API support, so many existing Node native addons can run with little or no change. The test runner was also rebuilt around Vitest, running real tests on a real device. More: https://t.co/MKDrMVw0vl https://t.co/c2PITTnAaG

    75162011K viewsView on X
  • Jul 8, 20262.6x their median

    OpenJS Security Update ⚠️ This quarter brought: - Node.js 26 release - major security release addressing 18 vulnerabilities - Removal of the security embargo requirement, - new LLM-assisted report classifier and web viewer for release management. - OpenJS CNA passed its one-year milestone - Ulises Gascón joined Alpha-Omega as an AI Security Engineer in Residence And more in our update blog: https://t.co/jOCgxNiSj8 As always, thank you to our friends at @AlphaOmegaOSS

    219318.2K viewsView on X
  • Aug 20, 20262.4x their median

    What happens when the Node.js community gets together to talk about the future? A lot. 👀 Node.js Interactive 2026 brought developers, maintainers, speakers, and open source leaders together in Atlanta for conversations about the technology and, just as importantly, the people behind it. And there was a reminder worth repeating: open source infrastructure runs on people. Supporting maintainers and strengthening communities is how we keep the ecosystem moving forward. Catch up on the conversations and takeaways from Node.js Interactive 2026 👇 https://t.co/96bKhuP97c Thank you @aviv_keller for the post. And thank you @RenderATL for having us. WE LOVE OUR COMMUNITY!

    2620311K viewsView on X
  • Mar 31, 2026

    Lodash gets 100M+ downloads a day. For years, it was primarily maintained by one person: @jdalton Then life happened. He stepped back. Now Lodash is entering a new phase with shared governance and support from the OpenJS Foundation. Big reminder: Open source isn’t just code. It’s people. Read more about our conversation with John-David here: https://t.co/aLvRmHV3CZ

    1972114K viewsView on X
  • Apr 8, 2026

    Understanding JavaScript security is more important than ever 👀 Check out our free training course to better spot security flaws in JavaScript apps, design safer systems, and bring a security-first mindset to every stage of development. Details here: https://t.co/6NH7Ub30JG https://t.co/vGGOLyFvze

    224103.0K viewsView on X
  • Jun 23, 20261.9x their median

    Node.js Interactive is back. If you've been part of the Node.js community for a while, you know what that name means — honest technical conversations, maintainers at the center, and real talk about what it takes to build production systems at scale. This August, Node.js Interactive returns as a dedicated track inside RenderATL 2026 in Atlanta, Georgia (August 12–13). It's included with a RenderATL conference pass. Expect programming on: → Node.js runtime performance → Security and supply chain resilience → AI-enabled developer tooling → Open source sustainability and platform engineering Whether you're a Node.js contributor, infrastructure engineer, or senior technical lead, this is worth your time. Read more and plan your trip → https://t.co/JXWl29Y5Xq

    195107.2K viewsView on X
  • Sep 25, 20261.8x their median

    Finding vulnerabilities is only part of open source security. Maintainers still need resources to triage, patch, and ship secure releases. The new OpenJS Security Stewardship Program will fund researchers and maintainers, starting with Node.js. https://t.co/gBxdqt9mBX https://t.co/BZNLXOz2Lh

    155409.3K viewsView on X
  • Oct 6, 20261.7x their median

    🔄 Node.js is changing how it approaches major releases. Node.js 26 will be the final release under the project’s twice-yearly model. Starting with Node.js 27, new major versions will follow an annual release schedule, giving developers a more predictable lifecycle to plan around. But a clearer release schedule does not automatically move production applications forward. If your application is still tied to Node.js 12, 14, 16, 18, or 20, upgrading may require dependency updates, compatibility testing, and changes to application behavior. @TuxCare_ 's Endless Lifecycle Support provides ongoing CVE patches for these Node.js versions, so you can keep your application protected while working toward a supported release. Learn more: https://t.co/sG9jw2nWHF

    166002.9K viewsView on X
  • Jul 22, 20261.7x their median

    We’re happy to welcome three new members on the OpenJS Foundation Board of Directors, and three that were re-elected! Together, they are filling positions on the Gold, Silver and Community level. - @abbycabs is now our board chair - Matt Hernandez, @ljharb and Aaron Mitchell join as board directors - @joe_sepi and @matteocollina have been re-elected as CPC directors We are honored to have their expertise at the OpenJS Foundation! More here: https://t.co/TZBcK6Dzaf

    136128.6K viewsView on X

Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.

Recurring topics

#nodejs#opensource

The most frequent hashtags in the sampled posts. They describe what this account writes about; they are not a performance signal, and the catalog-wide breakdown on the hub shows how little hashtag count moves.

Buy or sell Twitter (X) accounts - escrow-protected

PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 13 interactions against 318K followers, an engagement rate of 0.004%. Posts are seen about 3.7K times each, and 0.355% of those impressions turn into an interaction. That is about 1.15% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.27 posts a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 13:00 UTC, and Tuesday is the busiest day of the week. Of the 5 posts sampled, 40% carry an image or video and 100% link out. The account's strongest tracked post pulled 125 interactions, about 9.6x its own typical post. Recurring topics include #nodejs, #opensource. Only 5 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.

What is OpenJS Foundation's engagement rate on X?
OpenJS Foundation (@openjsf) has an engagement rate of 0.004%, based on the median interactions across 5 original posts from the last 30 days against 317,517 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.004%, OpenJS Foundation sits above the 10th percentile of the 204,424 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
Does @openjsf have real engagement?
There is not yet enough sample to rank this account against others of its size.
When does @openjsf post?
Most posts go out around 13:00 UTC, and Tuesday is its busiest day, at roughly 0.27 posts per day across the measured window.

Keep going