Skip to content

messaging proposal for WASI

active 2023-08-152026-03-09 (UTC)

Complete coverage26,650 / 26,650 hourly files (100%) · 2 absent upstream2023-08-152026-08-29 (UTC)
Events
401
Pushes
10
Pull requests
21
Issues
14
Stars
17
Forks
7

Activity over time

Daily event counts in the loaded window

Line chart, 938 days from 2023-08-15 to 2026-03-09. Pushes: 10 total, peak 2 in a day. Pull requests: 21 total, peak 2 in a day. Issues: 14 total, peak 6 in a day. Comments: 178 total, peak 28 in a day. Stars: 17 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
thomastaylor3121091557
danbugs985843
yordis670032
lukewagner330021
devigned16008
Mossaka14443
jocrau12006
dicej6003
brooksmtownsend4002
rvolosatovs3020
Zetanova2000
andrewweston2020
ricochet1001
andrew-goldie1000
guest2713141001
fibonacci17291000
endocrimes1001

Recent activity

Latest issues, pull requests and releases

  • Pull request#35andrewweston2025-10-16 05:37
  • Pull request#35andrewweston2025-10-16 05:37
  • Pull request#34thomastaylor3122025-07-10 22:58
  • Pull request#34thomastaylor3122025-07-09 23:26
  • Issue#33andrew-goldie2025-05-23 00:28
    What is the intended mechanism for an incoming-handler to configure subscription topics?
  • Issue#32Zetanova2025-04-12 10:03
    Feat: Batch processing
  • Issue#31Zetanova2025-04-12 09:56
    Feat: Pending Messages
  • Issue comment#29Mossaka2025-02-25 06:04
    refactor: make message property setters fallible
  • Issue comment#30danbugs2024-12-05 21:28
    Expected host behavior when message properties are not supported for implementation
  • Issue#30rvolosatovs2024-12-05 11:26
    Expected host behavior when message properties are not supported for implementation
  • Pull request#29rvolosatovs2024-12-05 11:14
  • Pull request#28danbugs2024-12-04 18:09
  • Pull request#28rvolosatovs2024-12-04 16:25
  • Pull request#27danbugs2024-11-07 00:23
  • Pull request#27danbugs2024-11-06 22:34
  • Issue comment#26ricochet2024-10-31 16:25
    Release `wasi-messaging@0.2.0`
  • Pull request#24danbugs2024-10-30 17:50
  • Issue comment#13guest2713142024-10-29 03:57
    Investigate using Native Messaging protocol for network (cloud) messaging
  • Issue comment#24danbugs2024-10-28 23:33
    Simplifies wasi-messaging interface with feedback
  • Issue comment#26thomastaylor3122024-10-09 18:43
    Release `wasi-messaging@0.2.0`
  • Issue#26danbugs2024-10-04 00:24
    Release `wasi-messaging@0.2.0`
  • Issue#25danbugs2024-10-04 00:21
    Update `wasi-messaging` to start using `@since` gates
  • Issue#14danbugs2024-10-04 00:19
    Should `wasi:messaging/messaging-guest/handler` take a `channel` parameter?
  • Issue#15danbugs2024-10-04 00:19
    Should `guest-configuration` include a `client` field?
  • Issue comment#15danbugs2024-10-04 00:19
    Should `guest-configuration` include a `client` field?

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 17 stars here means stars gained during the window, not the repo's star count.