npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@obinexusltd/lua-polycall

v1.0.0

Published

Protocol-compliant Lua binding for LibPolyCall — adapter pattern interface to the polycall.exe runtime

Readme

@obinexusltd/lua-polycall

Protocol-compliant Lua binding for LibPolyCall — part of the OBINexus toolchain.

Architecture: This binding acts as an adapter to the polycall.exe runtime. It does not execute user logic directly; all execution routes through the LibPolyCall binary following the program-first architecture paradigm.


Installation

Via npm (distributes the Lua sources)

npm install @obinexusltd/lua-polycall

Via LuaRocks (installs the Lua modules)

luarocks install lua-polycall-1.0-1.rockspec

Prerequisites

| Dependency | Version | |---|---| | Lua | >= 5.3, < 5.5 | | luasocket | >= 3.0 | | luasec | >= 1.0 | | lua-cjson | >= 2.1 | | polycall.exe | runtime binary (LibPolyCall v1) |


Usage

CLI

# After luarocks install or npm install -g
lua-polycall info
lua-polycall test --verbose
lua-polycall telemetry
lua-polycall --help

Lua API

local polycall = require('polycall')

local client = polycall.new_client({
    polycall_host = "localhost",
    polycall_port = 8084,
})

local ok, err = client:connect()
if not ok then error(err) end

local ok, err = client:authenticate({
    username = "user",
    api_key  = "your-api-key",
})
if not ok then error(err) end

local result, err = client:execute_operation("my_operation", { key = "value" })

client:shutdown()

Node.js helper (spawn from JS)

const { runSync, run } = require('@obinexusltd/lua-polycall');

// Synchronous
const { status, stdout } = runSync(['info']);
console.log(stdout);

// Async (inherits stdio)
run(['test', '--verbose']);

Module structure

polycall/
  init.lua                  ← main require('polycall') entry
  core/
    binding.lua             ← client factory & lifecycle
    protocol.lua            ← protocol handler
    state.lua               ← finite-state machine
    telemetry.lua           ← silent protocol observer
    auth.lua                ← zero-trust auth
  config/
    manager.lua
    validator.lua
  cli/
    main.lua                ← full CLI framework
    registry.lua            ← command registry
    commands/
      info.lua
      test.lua
      telemetry.lua
  utils/
    logger.lua
    validator.lua
    crypto.lua
  exceptions/
    protocol.lua
    connection.lua
  validators/
    setup.lua
    runtime.lua
    ssh.lua
bin/
  lua-polycall              ← CLI entry script (#!/usr/bin/env lua)
config/
  lua-polycall.conf
  lua.polycallrc

Architecture

lua-polycall enforces the adapter pattern:

  • The Lua layer translates calls into the LibPolyCall wire protocol.
  • polycall.exe performs all business logic execution.
  • Every state transition is validated by a finite automaton (polycall.core.state).
  • Authentication follows a zero-trust model — credentials are cryptographically validated per request.
  • A silent telemetry observer records protocol events for debugging without side effects.

Development

# Run Lua module load check
npm test

# Lint with luacheck
npm run lint

# Install Lua modules via luarocks
npm run install:lua

# Run full test suite (requires busted)
busted --verbose

Project

Part of the OBINexus engineering stack.
Technical lead: Nnamdi Michael Okpala — OBINexusComputing
License: MIT
Issues: https://github.com/obinexus/lua-polycall/issues