openfin-notifications
Client library for the Openfin Notifications Center
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bundled UI library; used in dist output rather than direct import in source. | ai | |
| phantom-deps | phantom-dep:semver-compare | AI (phantom-deps): Utility likely consumed via bundled dist; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): UI styling library used in bundled dist output; stable false positive. | ai | |
| phantom-deps | phantom-dep:openfin-service-async | AI (phantom-deps): OpenFin internal dep consumed via bundled dist; stable false positive. | ai | |
| phantom-deps | phantom-dep:openfin-service-signal | AI (phantom-deps): OpenFin internal dep consumed via bundled dist; stable false positive. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.12.7 | 5 / 0 | |
| 2.12.6 | 5 / 0 | |
| 2.12.5 | 5 / 0 | |
| 2.12.4 | 5 / 0 | |
| 2.12.3 | 5 / 0 | |
| 2.12.2 | 5 / 0 | |
| 2.12.1 | 5 / 0 | |
| 2.12.0 | 5 / 0 | |
| 2.11.6 | 5 / 0 | |
| 2.11.5 | 5 / 0 | |
| 2.11.4 | 5 / 0 | |
| 2.11.3 | 5 / 0 | |
| 2.11.2 | 5 / 0 | |
| 2.11.1 | 5 / 0 | |
| 2.11.0 | 5 / 0 | |
| 2.9.3 | 5 / 0 | |
| 2.9.2 | 5 / 0 | |
| 2.7.4 | 5 / 0 | |
| 2.7.3 | 5 / 0 |
v2.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.