# sap Published articles for sap. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## German optics giant ditches greenfield SAP migration DevFeed: [German optics giant ditches greenfield SAP migration]() Original publisher: [Read original article]() Author: Lindsay Clark Published: 2026-09-10T09:45:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [migration]() Tags: [enterprise](), [erp](), [migration](), [platform](), [sap](), [software]() ### AI overview A German optics company has dropped a greenfield SAP migration approach. Its revised plan moves the existing landscape to a new platform to achieve faster progress. ### Source excerpt 'Realigned' project plan aims to move existing landscape to new platform to 'achieve faster progress' ## Unbiased Java CPU profiling with JFR in JDK 25 DevFeed: [Unbiased Java CPU profiling with JFR in JDK 25]() Original publisher: [Read original article]() Author: Jaroslav Bachorík; Scott Gerring Published: 2026-07-22T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [cpu]() Tags: [agents](), [amazon](), [community](), [cpu](), [event](), [internals](), [java](), [latency](), [optimization](), [performance](), [production](), [sap](), [scale](), [traces]() ### AI overview The article explains why existing JVM sampling can misrepresent CPU-bound hotspots and describes a new JFR CPU profiling event introduced in JDK 25. ### Source excerpt Modern Java profilers often rely on unsupported JVM internals for accurate CPU profiling. Here's how engineers from Datadog, SAP, Amazon, and the OpenJDK community helped bring a new CPU profiling event to JDK 25. ## Chainguard artifacts safe from npm supply chain attack targeting SAP developer dependencies with 2.25M+ monthly downloads DevFeed: [Chainguard artifacts safe from npm supply chain attack targeting SAP developer dependencies with 2.25M+ monthly downloads]() Original publisher: [Read original article]() Published: 2026-04-29T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [npm](), [npm packages](), [chainguard](), [GitHub](), [container images](), [Bun](), [Node.js]() Tags: [bun](), [chainguard-containers](), [chainguard-libraries](), [github](), [malicious-packages](), [mini-shai-hulud](), [node-js](), [npm](), [npm-malware](), [npm-worm](), [sap](), [security](), [shai-hulud](), [supply-chain](), [tokens]() ### AI overview A Shai-Hulud-style npm supply-chain attack compromised four SAP Cloud Application Programming Model dependencies with more than 2.25 million combined monthly downloads. The malicious packages used a preinstall hook to download Bun and harvest GitHub tokens, npm tokens, and other developer secrets. Chainguard customers were protected because Chainguard Libraries for JavaScript does not build or serve packages containing install-time scripts, and Chainguard Factory terminated rebuilds when it detected the hook. ### Source excerpt New npm worm targets 2.25M-download packages. Chainguard customers stayed protected by blocking install-time scripts and malicious dependencies. ## "A Mini Shai-Hulud Has Appeared": Bun-Based Stealer Hits SAP @cap-js and mbt npm Packages DevFeed: ["A Mini Shai-Hulud Has Appeared": Bun-Based Stealer Hits SAP @cap-js and mbt npm Packages]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2026-04-29T00:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [incident](), [releases]() Tags: [article](), [awareness](), [ci-cd](), [developer](), [devops](), [ecosystem](), [github](), [github-actions](), [incident](), [interest](), [javascript](), [node-js](), [npm-packages](), [open-source-security](), [payload](), [releases](), [sap](), [scm](), [security](), [snyk-open-source](), [snyk-security-intel](), [supply-chain](), [supply-chain-security](), [tech](), [tool](), [toolchain](), [vulnerability-insights]() ### AI overview A supply-chain attack compromised four npm packages in the SAP development ecosystem. Malicious releases download Bun and execute an obfuscated credential stealer, while SAP published clean post-incident versions and Snyk issued advisories. ### Source excerpt A new npm supply chain attack self-branded "Mini Shai-Hulud" compromised four SAP-ecosystem packages on April 29, 2026. Snyk has live advisories. Here's the technical breakdown, IOCs, and what to do. ## A year of open collaboration: Celebrating the anniversary of A2A DevFeed: [A year of open collaboration: Celebrating the anniversary of A2A]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-04-16T20:55:00Z Content type: opinion Language: en Sources: [Google Open Source Blog]() Topics: [A2A protocol](), [Artificial Intelligence](), [Google](), [interoperability](), [Open Source](), [linux foundation](), [Security](), [Load Balancing]() Tags: [a2a](), [a2a-protocol](), [a2april](), [agent2agent](), [agents](), [ai](), [ai-agents](), [amazon](), [amazon-web-services](), [cisco](), [cryptographic](), [interoperability](), [linux-foundation](), [load-balancing](), [microsoft](), [open-source](), [sap](), [security](), [specifications](), [standard]() ### AI overview Google reflects on the first year of the Agent2Agent (A2A) protocol, including its donation to the Linux Foundation, the growth of its supporting ecosystem, and the release of A2A Protocol v1.0. The article highlights security, enterprise architecture, and interoperability improvements for multi-agent workflows. ### Source excerpt by Patricia Cruz, Google Open Source One year ago, on April 9th, 2025 Google announced the Agent2Agent(A2A) protocol. We saw the need for a "common language" that allows AI agents built on different frameworks to collaborate well across diverse systems. Then, on June 23, 2025 at the Open Source Summit North America in Denver, Mike Smith stood on stage to share a pivotal moment for the future of AI interoperability when Google officially donated the A2A protocol to the Linux Foundation, establishing it as a vendor-neutral, community-governed standard. This move was driven by a core belief: for AI agents to truly transform how we work and live, they must be able to communicate across framework boundaries and organizational silos without being locked into a single provider's ecosystem. By placing A2A under the neutral stewardship of the Linux Foundation, we opened the doors for the entire industry to build, contribute, and innovate together. A Foundation of Partners The formation of the A2A Project was made possible through the support of our founding members, including Amazon Web Services, Cisco, Microsoft, Salesforce, SAP, and ServiceNow. Over the past twelve months, this coalition has grown, with over 100 technology companies now supporting the project. From Prototype to Production The momentum since the donation has been remarkable. What began as a Google-led initiative has evolved into critical infrastructure for horizontal, peer-to-peer collaboration. Just one month ago, in March, the project reached a major milestone with the release of A2A Protocol v1.0, the first stable, fully production-ready version of the standard. Key achievements from the community this year include: Enhanced Security: The implementation of Signed Agent Cards for cryptographic identity verification, ensuring trust in multi-agent workflows. Web-Aligned Architecture: Refined specifications that support familiar load-balancing and security patterns for enterprise-scale deployments. Ecosystem