sspi-client
SSPI Client Library.
1
Versions
MIT
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
prasadt
Keywords
sspitedious
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): node-gyp rebuild is the standard install script for native Node.js addons; this package is a documented SSPI C++ binding with gypfile:true. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is a C++ header library for native addons; it is used at build time via gyp config, not imported in JS, so phantom-dep detection is a false positive here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 3 / 1 |
v0.1.0
2 findings
HIGH
Package has 'install' script
install-scripts
Script: node-gyp rebuild
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.