← Home

@nice-devone/common-sdk

npm Repository Homepage
4
Versions
—
License
No
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

seankirkbynice-devone-adminzach-colematejsimek

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): NICE Ltd. SDK with established publisher track record and 8 approved dependents; dormancy likely reflects release cadence, not takeover. ai
dependencies unvetted-dep:@testrtc/watchrtc-sdk AI (dependencies): WebRTC monitoring SDK consistent with CXone agent SDK use case; stable dependency across versions. ai
provenance no-provenance AI (provenance): Proprietary NICE Ltd. SDK; provenance attestation not expected for this publisher. ai
phantom-deps phantom-dep:react AI (phantom-deps): SDK re-exports/configures peer deps; phantom-dep false positive stable for this package. ai
phantom-deps phantom-dep:@testrtc/watchrtc-sdk AI (phantom-deps): Same pattern — declared for consumers, not directly imported in SDK source. ai
phantom-deps phantom-dep:react-toastify AI (phantom-deps): Same pattern — declared for consumers, not directly imported in SDK source. ai
phantom-deps phantom-dep:@reduxjs/toolkit AI (phantom-deps): Same pattern — declared for consumers, not directly imported in SDK source. ai

Versions (showing 4 of 4)

Version Deps Published
26.2.1 11 / 0
26.2.0 11 / 0
26.1.1 11 / 0
25.4.1 11 / 0

v26.2.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.2.0

1 finding
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.

v26.1.1

1 finding
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.

v25.4.1

1 finding
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.