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

@grayhaven/nerve-interop

v8.0.0

Published

Loss-aware standards, VEC subset, and factory interoperability primitives for Grayhaven Nerve.

Readme

@grayhaven/nerve-interop

Deterministic, loss-aware interoperability primitives for Grayhaven Nerve.

This package deliberately does not certify a harness, reproduce licensed standards text, supply normative acceptance values, implement an OPC UA transport, or parse official VEC XML. It provides four bounded building blocks:

  • standards profiles that identify exact authorities, revisions, scope, applicability, parameter sources, reviewers, and evidence layers;
  • a normalized structured VEC 2.2 subset adapter for connectors, pins, terminals, seals, and point-to-point wires;
  • transport-neutral OPC UA 40570 v1 job/result mappings for its initial single-core, single-layer cut/strip/crimp/seal scope; and
  • caller-parameterized automation-data and high-voltage design-readiness evaluations.

Important scope limits

Vec22SubsetDocument is an interchange DTO, not an XML parser and not proof of VEC conformance. The caller owns the official VEC XML XSD/ontology/SHACL toolchain and supplies validator identity, version, pass state, and report hash. Unknown extensions carry their source path and either lossless JSON or a raw artifact reference/hash so the adapter does not silently discard them. The public version and semantic-validation context is maintained by prostep ivip in the VEC 2.2.0 specification and compliance-test guidance.

The OPC mapping follows the public scope of OPC 40570 v1.0.0, published 2025-04-01: https://reference.opcfoundation.org/specs/OPC-40570. It is not an OPC UA client, binding, certificate, assembly protocol, or end-of-line tester protocol. It never invents a cut, strip, terminal, seal, or process value.

Automation findings evaluate only requirements selected by the caller. A profile may cite DIN 72036 or another source, but a result is not a DIN or other standards-conformity determination. High-voltage evaluation compares only caller-declared voltage domains against facts present in HIR. HIR does not currently establish HVIL function, physical segregation/clearance, or shield grounding, so those declarations remain unassessed. No hipot voltage, ramp, dwell, leakage, clearance, or insulation-resistance threshold is synthesized. The current publication identity for the automation-oriented design standard is DIN 72036:2026-04; this package contains none of its licensed rules.

Standards profiles may contain references and caller-controlled identifiers; they are not a home for copied tables, standard prose, acceptance values, or claims such as “certified” or “compliant.”