@webex/calling
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established Webex SDK package; missing description is benign metadata gap. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is uncommon; not a signal for this established package. | ai | |
| dependencies | unvetted-dep:@types/platform | AI (dependencies): Type definitions package; no runtime risk for this SDK. | ai | |
| dependencies | unvetted-dep:jest-html-reporters | AI (dependencies): Test reporter dependency; no runtime risk for consumers of this package. | ai | |
| phantom-deps | phantom-dep:@types/platform | AI (phantom-deps): Type-only dep used at compile time; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:jest-html-reporters | AI (phantom-deps): Test reporter referenced in jest config, not imported in source; stable false positive. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Buffer polyfill declared for bundler config; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 10 / 54 | |
| 3.11.0 | 10 / 54 | |
| 3.10.0 | 10 / 54 | |
| 3.9.0 | 10 / 52 | |
| 3.8.1 | 10 / 52 | |
| 3.7.0 | 9 / 52 | |
| 3.6.0 | 9 / 52 | |
| 3.3.1 | 9 / 52 | |
| 3.3.0 | 9 / 52 | |
| 3.2.0 | 9 / 52 | |
| 3.1.0 | 9 / 52 | |
| 3.0.1 | 9 / 52 |
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.