CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

@neoimpulse/cap-js-notifications

A copy of the official @cap-js/notifications plugin republished under another scope, whose README points at the original and says nothing about what was changed.

Facts

Latestv1.0.12ReleasedLast pushLicenceApache-2.0

Where it sits

Lives in
Provides
NotificationsCAPNotificationscapabilityTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.
Flavors
Node.jsfrom its runtime
Requires
@sap/cds≥ 9@sap/cdsartifactThe peer range, as published.

Who is behind it

neoimpulse GmbHneoimpulse GmbHOrganisationMaintains this
In the atlas: maintains 7
@neoimpulseGmbH
maintainerTiKeiNeoPersonContributes to this
In the atlas: contributes to 1
@TiKeiNeo
1 contributor

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →
PracticalFunctional boundary

Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.

What it declares

Every artifact

Type
CDS plugin
Origin
Independently maintained
Runtime
Node.js

As a CDS plugin

Declared for
>=9
Distributed through
does not say

Connections3

Install

npm add @neoimpulse/cap-js-notifications

Derived from the package name. No recipe recorded; the README has the configuration.

README

quoted from neoimpulseGmbH/cap-js-notifications under Apache-2.0, read
neoimpulseGmbH/cap-js-notifications/README.mdOn GitHub

CAP JS Notifications

Overview

CAP JS Notifications is a CDS plugin designed to provide an easy action for the notification service. It supports sending notifications to different destinations based on the environment configuration.

Note: This project is a copy of the cap-js/notifications repository. Please refer to the original repository for more details.

Features

  • Send notifications to REST endpoints or console based on the environment.
  • Validate and process notification types.
  • Deploy notification types to the notification service. The deployment is skipped for the notify-to-console kind, as there is no service to deploy to, and a failing deployment is logged as a warning instead of preventing the server from starting.
  • Customizable notification templates.

Installation

To install the dependencies, run:

npm install

Usage

Configuration

The plugin configuration is defined in the package.json file under the cds.requires.notifications section. It includes settings for different environments, notification types, and destinations.

Notification Types

Notification types are defined in the srv/notification-types.json file. Each notification type includes templates for different languages and versions.

Running the Plugin

To run the plugin, use the following command:

cds run
Building the Project

To build the project, use the following command:

cds build
Releasing the Project

The release process is automated using GitHub Actions. The configuration is defined in the .github/workflows/release.yml file.

License

This project is licensed under the Apache License 2.0. See the LICENSE file for more details.

Contributing

Contributions are welcome! Please read the CONTRIBUTING guidelines before submitting a pull request.

Contact

For any questions or issues, please contact the author at Neoimpulse GmbH.

Apache-2.0, read

History

Latest

v1.0.12

Notes
Bug Fixes
  • never let notification types deployment block startup (7e73477)
  1. v1.0.11

    Notes
    Bug Fixes
  2. v1.0.10

    Notes
    Bug Fixes
    • upgrade @sap/cds and @sap/cds-dk to v9 (a36bbb8)
  3. v1.0.9

    Notes
    Bug Fixes
  4. v1.0.8

    Notes
    Bug Fixes
    • Added build notification (d4e84aa)
  5. v1.0.7

    Notes
    Bug Fixes
    • Added build notification (7cfd0a1)
  6. v1.0.6

    Notes
    Bug Fixes
    • Added build notification (c26c567)
  7. v1.0.5

    Notes
    Bug Fixes
    • Added build notification (7068f39)
  8. v1.0.4

    Notes
    Bug Fixes
    • Added build notification (d98fa2e)
  9. v1.0.3

    Notes
    Bug Fixes
    • Added build notification (2f5732a)
    • Added build notification (291422f)
  10. v1.0.2

    Notes
    Bug Fixes
    • Added build notification (95ace2f)
  11. v1.0.1

    Notes
    Bug Fixes
    • updated semantic-release (a8e7845)
    • updated semantic-release (0ac902b)
  12. v1.0.0

    Notes
    Bug Fixes
    • updated semantic-release (d57881e)
    • updated semantic-release (eb5da04)
105downloads per week, npm
Weekly downloads for @neoimpulse/cap-js-notifications26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 105.20 Apr – 26 Apr: 13827 Apr – 3 May: 2544 May – 10 May: 11711 May – 17 May: 14818 May – 24 May: 15325 May – 31 May: 1311 Jun – 7 Jun: 878 Jun – 14 Jun: 5315 Jun – 21 Jun: 9422 Jun – 28 Jun: 10829 Jun – 5 Jul: 876 Jul – 12 Jul: 8513 Jul – 19 Jul: 7420 Jul – 26 Jul: 12027 Jul – 2 Aug: 543 Aug – 9 Aug: 9410 Aug – 16 Aug: 7817 Aug – 23 Aug: 4624 Aug – 30 Aug: 5531 Aug – 6 Sept: 687 Sept – 13 Sept: 6714 Sept – 20 Sept: 3821 Sept – 27 Sept: 10328 Sept – 4 Oct: 695 Oct – 11 Oct: 12212 Oct – 18 Oct: 105
Declared alternative
  1. @cap-js/notificationsBusiness notifications from CAP to SAP Build WorkZone
Notifications
  1. aditheos/ApplicationLogsNotificationToFioriFiori launchpad notification for application log errorsfrom ABAP
  2. agiguere/SCPmsPushNotificationREST_APIABAP classes sending push notifications to Mobile Servicesfrom ABAP
  3. ABAP-PRCFramework for multi-step ABAP processes with monitoringfrom ABAP
  4. com.sap.cds:cds-feature-notificationsBusiness notifications from CAP Java via SAP Alert Notificationfrom CAP
  5. @cap-js/notificationsBusiness notifications from CAP to SAP Build WorkZonefrom CAP
  6. @cap-rp/notificationsRenamed copy of @cap-js/notifications under another scopefrom CAP
  7. DryDumbHead/easyHtmlEmailABAP helper class building HTML emails from templatesfrom ABAP
  8. @expertum/cap-email-pluginAnnotation-driven mail on CAP entity lifecycle eventsfrom CAP
  9. peterlangner/zrssRSS feed publisher for content from an SAP NetWeaver ABAP systemfrom ABAP

Details

Sources5
npm registrydiscovered here, cds-pluginchecked
npm registrydiscovered here, @cap-jschecked
npm registry, @neoimpulse/cap-js-notificationsversion, releases, installschecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
declared for>=9
latestv1.0.12
first release
releases and cadence13, ~0d median
discovered vianpm registry · cds-plugin, npm registry · @cap-js
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
Contributors1

From the repository’s contributor list, .

History in the atlas2
  1. fork of artifact:cap-js-notifications
  2. First seen.
For your agent
Ref
artifact:neoimpulse-cap-js-notifications
JSON
/artifacts/neoimpulse-cap-js-notifications.json
MCP
Connecting an agent