@stigg/node-server-sdk
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal paired with trusted publisher and no code changes; consistent with internal team changes at Stigg. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher stiggnpc has strong track record; maintainer rotation consistent with org restructuring, not takeover. | ai | |
| dependencies | unvetted-dep:redlock | AI (dependencies): redlock beta is an intentional dependency for distributed locking; stable pattern across this package's versions. | ai | |
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): lru-cache is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/fragment-matcher | AI (phantom-deps): Declared runtime dependency; false positive for this package. | ai | |
| phantom-deps | phantom-dep:husky | AI (phantom-deps): husky is declared in dependencies (used for prepare script); false positive. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived package predating common provenance adoption; no other risk signals. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a peer/optional dep re-exported via isomorphic-ws; not directly imported by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK with 378 versions; sparse README is a style choice, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@bitauth/libauth | AI (phantom-deps): Crypto utility used via @stigg/* packages; phantom-dep is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:redlock | AI (phantom-deps): redlock is an optional Redis locking dep; not directly imported in core SDK. | ai | |
| phantom-deps | phantom-dep:ioredis | AI (phantom-deps): ioredis is an optional Redis integration dep; not directly imported in core SDK. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs used transitively through @stigg/* packages; phantom-dep is a stable false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.42.0 | 21 / 8 | |
| 4.41.0 | 21 / 8 | |
| 4.38.0 | 21 / 8 | |
| 4.36.0 | 20 / 8 | |
| 4.30.0 | 21 / 8 | |
| 4.29.3 | 21 / 8 | |
| 4.29.0 | 21 / 8 | |
| 4.24.0 | 21 / 8 | |
| 4.22.2 | 21 / 8 | |
| 4.12.0 | 20 / 29 | |
| 4.9.0 | 20 / 29 | |
| 4.8.0 | 20 / 29 | |
| 4.7.0 | 20 / 29 | |
| 4.3.1 | 20 / 29 | |
| 4.2.1 | 20 / 29 | |
| 4.2.0 | 20 / 29 | |
| 4.1.0 | 20 / 29 |
v4.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.