@voyantjs/notifications-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/admin/notification-deliveries-host.js | AI (source-diff): Readable compiled ESM/JSX; long lines are bundled React component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/admin/notification-reminder-rules-host.js | AI (source-diff): Readable compiled ESM/JSX; long lines are bundled React component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/components/notification-settings-form.js | AI (source-diff): Readable compiled ESM/JSX; long lines are bundled React component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/components/stage-editor-dialog.js | AI (source-diff): Readable compiled ESM/JSX; long lines are bundled React component output, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; legitimate workflow change. | ai | |
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation which supersedes gitHead as a supply chain integrity signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped org package with clear repo and exports; missing description is cosmetic, not a risk signal here. | ai |
Versions (showing 12 of 229)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 1 / 11 | |
| 0.15.0 | 1 / 11 | |
| 0.14.0 | 1 / 11 | |
| 0.13.0 | 1 / 11 | |
| 0.12.0 | 1 / 11 | |
| 0.11.0 | 1 / 11 | |
| 0.10.0 | 1 / 11 | |
| 0.9.0 | 1 / 11 | |
| 0.8.0 | 1 / 11 | |
| 0.7.0 | 1 / 11 | |
| 0.6.9 | 1 / 11 | |
| 0.6.8 | 1 / 11 |
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.10.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.9.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.8.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.6.9
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.