IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Add a new idea Subscribe
Status Submitted
Workspace Cognos Analytics
Components Security
Created by Guest
Created on Jun 23, 2026

RELATED IDEAS

Remove development dependencies from node-services/services/.../package-lock.json in release artifacts

Description
In the current release packaging, package-lock.json under node-services/services/... includes development dependencies that are not used at runtime. Security scanners still parse these entries and repeatedly flag vulnerabilities (for example, legacy lodash versions), creating false positives and recurring audit noise.

This causes unnecessary remediation cycles, repeated exception handling, and avoidable effort across security and operations teams.

Requested Enhancement
Please update the build/release process to exclude development dependencies from shipped lock/manifests in product artifacts (or publish a production-only lock file).
Specifically, ensure that only runtime dependencies are present in distributed package-lock.json files for release builds.

Business/Operational Impact

Reduces recurring false-positive vulnerability findings
Improves scan accuracy and compliance reporting
Lowers operational overhead for security triage and audit responses
Prevents repeated tickets/escalations for non-runtime components

Expected Outcome / Acceptance Criteria

Release artifacts contain runtime dependencies only
Development dependencies are excluded from production manifests/lock files
Security scans no longer report vulnerabilities originating from dev-only packages in shipped artifacts

Needed By Month

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.