vpulim/node-soap

A SOAP client and server for node.js.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 22nd, 2026
Created on April 7th, 2011
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 1,489
Total Stargazers: 3,037 (+0)
Total Subscribers: 98 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.0 hours
Mean response time: 627.9 days
90th percentile: 3503.1 days
Tracked items: 182

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 214 days
Stale 30+ days: 5
Stale 90+ days: 4

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 6
Events in 7 days: 13

Top labels

  • needs pull request (19)
  • bug (13)
  • awaiting response (7)
  • NS Prefix Bug (6)
  • Discussion (4)
  • enhancement (4)
  • no activity for extended period (4)
  • WSDL Bug (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

node-soap is a SOAP client and server for Node.js that enables communication with web services using the SOAP protocol.

The tool addresses the need to integrate with SOAP-based web services in Node.js environments. It works by providing both client functionality to connect to existing SOAP services and server functionality to build and expose your own SOAP services. The module handles the complexity of SOAP message construction, XML parsing, and protocol handling, abstracting these details away from the developer.

Developers should adopt this tool if they need to work with legacy or enterprise systems that expose SOAP interfaces, or if they are building SOAP services themselves in a Node.js stack. It suits projects that require standards-compliant SOAP communication. The README emphasizes setting the forceUseSchemaXmlns option to true for best SOAP specification support, though it defaults to false for backward compatibility, which is an important consideration for new implementations.

The project maintains active engagement with its codebase through regular updates and accepts external contributions. Development activity shows consistent attention to both bug fixes and feature requests from the community. The tool receives ongoing support from a sponsor organization that contributes engineering resources to the project.