← Home

@syncfusion/ej2-notifications

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

syncfusionorgessentialjs2syncfusion-javascript

Keywords

ej2syncfusionweb-componentsjavascripttypescriptej2-notification-componentsej2-badgebadgesej2-toasttoasttoasternotificationnotification badgecircle badgebadge csstoast cssalart

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Syncfusion packages have large link-heavy READMEs by design; not phishing or spam. ai
dependencies unvetted-dep:@syncfusion/ej2-base AI (dependencies): Sibling Syncfusion EJ2 package at matching version; expected dependency pattern. ai
dependencies unvetted-dep:@syncfusion/ej2-popups AI (dependencies): Sibling Syncfusion EJ2 package at matching version; expected dependency pattern. ai
dependencies unvetted-dep:@syncfusion/ej2-buttons AI (dependencies): Sibling Syncfusion EJ2 package at matching version; expected dependency pattern. ai

Versions (showing 9 of 9)

Version Deps Published
33.2.7 3 / 0
33.2.3 3 / 0
33.1.49 3 / 0
33.1.44 3 / 0
32.2.3 3 / 0
32.1.24 3 / 0
32.1.22 3 / 0
32.1.19 3 / 0
31.2.12 3 / 0

v33.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v33.1.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v33.1.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v32.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v32.1.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.1.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v32.1.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v31.2.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.