← Home

@novu/react

Novu <Inbox /> React SDK

26
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

scopsyletitrockhimanshu-novuchmarax

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established publisher with strong track record; no material code changes; provenance gap alone is not disqualifying. ai
provenance no-provenance AI (provenance): Novu ecosystem package; lack of Sigstore attestation is a process gap, not a security indicator for this package. ai

Versions (showing 26 of 26)

Version Deps Published
3.18.1 1 / 7
3.18.0 1 / 7
3.17.0 1 / 7
3.16.0 1 / 7
3.15.0 1 / 7
3.11.0 1 / 7
3.10.1 1 / 7
3.10.0 1 / 7
3.9.3 1 / 7
3.9.2 1 / 7
3.9.1 1 / 7
3.8.2 1 / 7
3.8.1 1 / 7
3.8.0 1 / 7
3.7.1 1 / 7
3.7.0 1 / 7
3.6.0 1 / 7
3.5.0 1 / 7
3.4.0 1 / 7
3.3.1 1 / 7
3.3.0 1 / 7
3.2.0 1 / 7
3.1.0 1 / 7
3.0.3 1 / 7
3.0.1 1 / 7
3.0.0 1 / 7

v3.18.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.18.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.0

1 finding
INFO No provenance attestation provenance

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

v3.0.3

1 finding
INFO No provenance attestation provenance

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

v3.0.1

1 finding
INFO No provenance attestation provenance

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

v3.0.0

1 finding
INFO No provenance attestation provenance

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