@openfin/fdc3-api
OpenFin fdc3 module utilities and types.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:openfin-adapter | AI (dependencies): openfin-adapter is a bundled dependency (bundleDependencies) from OpenFin's own monorepo; file: path is irrelevant at install time. | ai | |
| npm-metadata | url-dep:openfin-adapter | AI (npm-metadata): Listed in bundleDependencies; the file: path is bundled at publish time, not resolved from the registry by consumers. | ai | |
| phantom-deps | phantom-dep:openfin-adapter | AI (phantom-deps): Bundled dependency; not directly imported as a module import is expected for this pattern. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 46.100.4 | 2 / 0 | |
| 46.100.3 | 2 / 0 | |
| 46.100.2 | 2 / 0 | |
| 46.100.1 | 2 / 0 | |
| 45.100.94 | 2 / 0 | |
| 45.100.93 | 2 / 0 | |
| 45.100.92 | 2 / 0 | |
| 45.100.91 | 2 / 0 | |
| 45.100.90 | 2 / 0 | |
| 45.100.89 | 2 / 0 | |
| 45.100.88 | 2 / 0 | |
| 45.100.87 | 2 / 0 | |
| 45.100.86 | 2 / 0 | |
| 45.100.85 | 2 / 0 | |
| 45.100.84 | 2 / 0 | |
| 45.100.83 | 2 / 0 | |
| 45.100.81 | 2 / 0 | |
| 45.100.79 | 2 / 0 | |
| 45.100.78 | 2 / 0 | |
| 45.100.77 | 2 / 0 | |
| 45.100.76 | 2 / 0 | |
| 45.100.75 | 2 / 0 | |
| 45.100.74 | 2 / 0 | |
| 45.100.73 | 2 / 0 | |
| 45.100.72 | 2 / 0 | |
| 45.100.71 | 2 / 0 | |
| 45.100.70 | 2 / 0 | |
| 45.100.68 | 2 / 0 | |
| 45.100.67 | 2 / 0 | |
| 45.100.65 | 2 / 0 | |
| 45.100.64 | 2 / 0 | |
| 45.100.63 | 2 / 0 | |
| 45.100.62 | 2 / 0 | |
| 45.100.61 | 2 / 0 | |
| 45.100.60 | 2 / 0 | |
| 45.100.59 | 2 / 0 | |
| 45.100.58 | 2 / 0 | |
| 45.100.56 | 2 / 0 | |
| 45.100.55 | 2 / 0 | |
| 45.100.51 | 2 / 0 | |
| 45.100.50 | 2 / 0 | |
| 45.100.49 | 2 / 0 | |
| 45.100.48 | 2 / 0 | |
| 45.100.47 | 2 / 0 | |
| 45.100.46 | 2 / 0 | |
| 45.100.45 | 2 / 0 | |
| 45.100.43 | 1 / 0 | |
| 45.100.42 | 1 / 0 | |
| 44.101.3 | 2 / 0 | |
| 44.101.2 | 2 / 0 | |
| 44.101.1 | 2 / 0 |
v46.100.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v45.100.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.100.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.101.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.101.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.