HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
second-state
wasmedge-quickjs
JavaScript2022–2023
second-state / wasmedge-quickjs

wasmedge-quickjs

A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge.

3Distinct people
4Mentions
0Explicit recommenders
566GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2022-08-25 01:57:57 UTC to 2023-11-05 01:20:59 UTC.

012022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 20222022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 20232023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC110
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC000
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC000
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC101
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC101
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC101

What Hacker News says

4 sources
I'm impressed you're already leveraging the component model. I thought it wasn't quite ready for primetime yet, but it seems you're proving that wrong... I'll have to dig in more here, as I'm working embedding WebAssembly in a high performance storage engine. Thanks for the notes! I hear you on QuickJS - I've seen approaches of folks trying to build more node compatibility on top of quickjs (ala https://github.com/second-state/wasmedge-quickjs), but have recently heard about spidermonkey in wasmtime. Do you have intuition for nodejs vs browser in terms of what people want in terms of compatibility?
In Spin 2.0 – open-source tool for building and running WASM apps
I’m excited to share an serverless code review bot I built that uses ChatGPT to automatically review PRs, summarize commits and spot issues. Deploy it in your GitHub repos in 5 minutes with no servers to manage. Say goodbye to wasted developer time and boost community contributions. The future of code review is automated, and it’s here! See 2 examples: Example 1: Analyze the content and risks of each commit in the PR. Then make a summary. https://github.com/WasmEdge/WasmEdge/pull/2394#issuecomment-... Example 2: Review the source code files in the PR one by one, analyze possible risks, and summarize the changes this time. It even gives suggested improvements to the code! https://github.com/WasmEdge/WasmEdge/pull/2428#issuecomment-... See potential problems #1 for its proposed changes https://github.com/second-state/wasmedge-quickjs/pul
Read the rest
l/82#iss... If you want this bot to try to review the PR you are interested in first, welcome to use our public playground. https://github.com/flows-network/review-any-pr-with-chatgpt The functions code is open source - check it out and let us know your feedback. You can also write a function of your own in minutes.
In ChatGPT-powered code review bot to boost your PR merge. Deploy in 5 mins
We built Flows.network, a serverless workflow automation platform, to give "eyes, ears, memory and hands" to large language models like GPT-4. LLM's are powerful but forgetful, and the ecosystem needs developer tools to build plugins and agents to extend their capabilities. Flows.network is integrated with LLMs and SaaS to enable: Processing prompts and acting on LLM results with your own code Adding memory to LLMs with storage of embeddings, conversation context, prompt management, and fine-tuning Triggering from web services and acting based on LLM outputs Supporting major LLMs like GPT-4, CLIP, and others across languages, images and multimedia We built a GitHub bot that automatically analyzes and summarizes pull requests in 5 minutes using GPT-4 and our lightweight WasmEdge sandbox. It's being used by several open source projects. Ex
Read the rest
amples of how great it works: Analyzing PR commits and risks: https://github.com/WasmEdge/WasmEdge/pull/2394#issuecomment-... Reviewing source code files, analyzing risks and summarizing changes. It even suggests code improvements! https://github.com/WasmEdge/WasmEdge/pull/2428#issuecomment-... See suggested code improvements: https://github.com/second-state/wasmedge-quickjs/pull/82#iss... Try the bot on a PR you're interested in: https://github.com/flows-network/review-any-pr-with-chatgpt Flows.network brings automation and tooling to simplify building complex AI workloads for startups. We believe Flows.network can become a flexible plugin for GPT-4 and other large language models. :) Come see how flows.network lets you create custom automation for ChatGPT and other LLM services with zero setup
In Flows.network: Add eyes, ears, memory& hands to LLMs with serverless functions

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.