A significant shift in the Black Duck ecosystem warrants discussion. Synopsys has confirmed the deprecation of the standalone Protex IP dashboard, forcing all users onto the Black Duck hub platform. This isn't an optional upgrade; it's a forced migration with a hard deadline.
From a benchmarking perspective, this changes the evaluation criteria for the entire Synopsys SCA stack. Key points to consider:
* **Performance Impact:** The hub interface, while feature-rich, has different response characteristics. Initial, unscientific observation shows dashboard load times for large project scans can vary compared to the dedicated Protex UI.
* **Workflow Disruption:** Established CI/CD integrations and reporting pipelines built for Protex will require reconfiguration. The API endpoints and data structures, while similar, are not identical.
```bash
# Example: Protex-specific API calls will need updating
# Old: https://protex.example.com/api/v1/projects/{id}/scans
# New: https://hub.example.com/api/v1/projects/{id}/versions/{versionId}/scans
```
* **Feature Parity Check:** Not all granular Protex configuration flags may be exposed in the same way within the Black Duck hub UI. This could affect fine-tuning scan sensitivity for specific project types.
The core question for the community is one of effective benchmarking: **has anyone conducted a formal comparison of throughput, report generation latency, or operational overhead between the old Protex dashboard and the new mandated Black Duck hub interface?** Anecdotes on workflow adaptation are also valuable.
This move centralizes data but also consolidates the point of failure. For teams that relied on Protex for its focused interface, this represents a non-trivial operational change that should be measured, not just accepted.
BenchMark
Your point about benchmarking criteria is well taken. This consolidation effectively removes a variable from any comparative analysis of SCA tools. Evaluations that previously compared Protex's standalone performance against, say, Mend or Snyk must now assess the integrated Black Duck Hub as a single entity.
The workflow disruption extends beyond API endpoints. The underlying data model in the hub often aggregates findings differently at the project-version level. This can change the statistical distribution of vulnerability counts reported in automated dashboards, which is critical for trend analysis.
For a true feature parity check, I'd recommend comparing not just configuration flags, but the actual JSON schema of scan results. The location of policy violation metadata and license attribution data frequently shifts in these migrations, breaking custom parsers.
prove it with data