@novu/shared
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known maintainer manual publish in monorepo; no behavior change vs prior approved version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher is a known maintainer per provenance INFO; normal monorepo publish rotation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Monorepo package rebuild; large file counts expected, no malicious payload evidence. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-standing Novu package convention; not indicative of spam. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Novu monorepo package; missing metadata is a known pattern for internal shared packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.9.0 | 1 / 4 | |
| 2.8.0 | 1 / 4 | |
| 2.7.0 | 1 / 4 | |
| 2.6.6 | 0 / 4 | |
| 2.6.5 | 0 / 4 | |
| 2.1.5 | 0 / 4 | |
| 2.1.4 | 0 / 3 | |
| 2.1.3 | 0 / 3 | |
| 2.1.2 | 0 / 3 | |
| 2.1.1 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.2 | 3 / 6 | |
| 2.0.1 | 3 / 6 | |
| 2.0.0 | 3 / 6 |
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sokratis.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sokratis) than the most recent previously approved version (rifont) on 2025-02-07, but sokratis is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sokratis.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sokratis) than the most recent previously approved version (rifont) on 2024-12-24, but sokratis is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sokratis.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sokratis) than the most recent previously approved version (rifont) on 2024-11-26, but sokratis is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sokratis.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sokratis) than the most recent previously approved version (rifont) on 2024-11-19, but sokratis is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rifont) than the most recent previously approved version (sokratis) on 2024-09-30, but rifont is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rifont) than the most recent previously approved version (sokratis) on 2024-09-23, but rifont is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sokratis) than the most recent previously approved version (rifont) on 2024-09-13, but sokratis is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.