@webex/internal-plugin-board
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:es6-promise-series | AI (dependencies): es6-promise-series is a small, stable utility; no known advisories and consistent use across this SDK's versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description in a large monorepo SDK; stable pattern across all @webex/* packages. | ai | |
| provenance | no-provenance | AI (provenance): CI-published monorepo package; no provenance is consistent across the @webex/* ecosystem. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 10 / 14 | |
| 3.11.0 | 10 / 14 | |
| 3.10.0 | 10 / 14 | |
| 3.9.0 | 10 / 14 | |
| 3.8.1 | 10 / 14 | |
| 3.8.0 | 10 / 14 | |
| 3.7.0 | 10 / 14 | |
| 3.6.0 | 10 / 14 | |
| 3.5.0 | 10 / 14 | |
| 3.4.0 | 10 / 14 | |
| 3.3.1 | 10 / 14 | |
| 3.3.0 | 10 / 14 | |
| 3.2.0 | 10 / 14 | |
| 3.1.0 | 10 / 14 | |
| 3.0.0 | 10 / 14 |
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.