@checkstack/integration-webex-backend
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @checkstack scoped package, consistent with the package's internal ecosystem pattern. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a legitimate license; consistent across versions. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Internal monorepo workspace dependency from the same @checkstack org; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@checkstack/integration-backend | AI (dependencies): Internal monorepo workspace dependency from the same @checkstack org; not a third-party risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal @checkstack integration package; missing description is consistent across the ecosystem, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack/* packages; no CI provenance setup in this ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped org package; missing metadata is expected for private/internal modules, not a spam indicator. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 5 / 4 | |
| 0.1.5 | 5 / 4 | |
| 0.1.4 | 5 / 4 | |
| 0.1.2 | 5 / 4 | |
| 0.0.32 | 4 / 3 | |
| 0.0.31 | 4 / 3 | |
| 0.0.30 | 4 / 3 | |
| 0.0.29 | 4 / 3 | |
| 0.0.28 | 4 / 3 | |
| 0.0.27 | 4 / 3 | |
| 0.0.26 | 4 / 3 | |
| 0.0.25 | 4 / 3 | |
| 0.0.24 | 4 / 3 | |
| 0.0.23 | 4 / 3 | |
| 0.0.22 | 4 / 3 | |
| 0.0.21 | 4 / 3 | |
| 0.0.20 | 4 / 3 | |
| 0.0.19 | 4 / 3 | |
| 0.0.18 | 4 / 3 | |
| 0.0.17 | 4 / 3 | |
| 0.0.15 | 4 / 3 | |
| 0.0.14 | 4 / 3 | |
| 0.0.13 | 4 / 3 | |
| 0.0.11 | 4 / 3 | |
| 0.0.10 | 4 / 3 | |
| 0.0.9 | 4 / 3 | |
| 0.0.8 | 4 / 3 | |
| 0.0.6 | 4 / 3 | |
| 0.0.5 | 4 / 3 | |
| 0.0.4 | 4 / 3 | |
| 0.0.3 | 4 / 3 |
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.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.