@hmcts/opal-frontend-common
[](https://www.npmjs.com/package/@hmcts/opal-frontend-common) [](https://github.com/hmcts/opal-frontend-common-ui-l
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from jenkins-reform-hmcts to GitHub Actions is a CI pipeline migration; SLSA attestation confirms integrity. | ai | |
| dependencies | unvetted-dep:home-office-kit | AI (dependencies): Expected dependency for HMCTS/Home Office frontend tooling; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@microsoft/applicationinsights-web | AI (dependencies): Microsoft Application Insights is a standard telemetry SDK; appropriate for government frontend monitoring. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for Angular/TypeScript compiled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:home-office-kit | AI (phantom-deps): Referenced in config files as documented; not a direct import pattern for this type of frontend library. | ai |
Versions (showing 92 of 92)
| Version | Deps | Published |
|---|---|---|
| 0.0.94 | 9 / 0 | |
| 0.0.93 | 9 / 0 | |
| 0.0.92 | 9 / 0 | |
| 0.0.91 | 9 / 0 | |
| 0.0.90 | 9 / 0 | |
| 0.0.89 | 9 / 0 | |
| 0.0.88 | 9 / 0 | |
| 0.0.87 | 9 / 0 | |
| 0.0.86 | 9 / 0 | |
| 0.0.85 | 9 / 0 | |
| 0.0.84 | 9 / 0 | |
| 0.0.83 | 9 / 0 | |
| 0.0.82 | 9 / 0 | |
| 0.0.81 | 9 / 0 | |
| 0.0.80 | 9 / 0 | |
| 0.0.79 | 9 / 0 | |
| 0.0.78 | 9 / 0 | |
| 0.0.77 | 9 / 0 | |
| 0.0.76 | 9 / 0 | |
| 0.0.75 | 9 / 0 | |
| 0.0.74 | 9 / 0 | |
| 0.0.72 | 9 / 0 | |
| 0.0.71 | 9 / 0 | |
| 0.0.70 | 9 / 0 | |
| 0.0.69 | 9 / 0 | |
| 0.0.68 | 9 / 0 | |
| 0.0.67 | 1 / 0 | |
| 0.0.66 | 1 / 0 | |
| 0.0.65 | 1 / 0 | |
| 0.0.64 | 1 / 0 | |
| 0.0.63 | 1 / 0 | |
| 0.0.62 | 1 / 0 | |
| 0.0.61 | 1 / 0 | |
| 0.0.60 | 1 / 0 | |
| 0.0.59 | 1 / 0 | |
| 0.0.58 | 1 / 0 | |
| 0.0.57 | 1 / 0 | |
| 0.0.56 | 1 / 0 | |
| 0.0.55 | 1 / 0 | |
| 0.0.54 | 1 / 0 | |
| 0.0.53 | 1 / 0 | |
| 0.0.52 | 1 / 0 | |
| 0.0.51 | 1 / 0 | |
| 0.0.50 | 1 / 0 | |
| 0.0.49 | 1 / 0 | |
| 0.0.48 | 1 / 0 | |
| 0.0.47 | 1 / 0 | |
| 0.0.46 | 1 / 0 | |
| 0.0.45 | 1 / 0 | |
| 0.0.44 | 1 / 0 | |
| 0.0.43 | 1 / 0 | |
| 0.0.42 | 1 / 0 | |
| 0.0.41 | 1 / 0 | |
| 0.0.40 | 1 / 0 | |
| 0.0.39 | 1 / 0 | |
| 0.0.38 | 1 / 0 | |
| 0.0.37 | 1 / 0 | |
| 0.0.36 | 1 / 0 | |
| 0.0.35 | 1 / 0 | |
| 0.0.34 | 1 / 0 | |
| 0.0.33 | 1 / 0 | |
| 0.0.32 | 1 / 0 | |
| 0.0.31 | 1 / 0 | |
| 0.0.30 | 1 / 0 | |
| 0.0.29 | 1 / 0 | |
| 0.0.28 | 1 / 0 | |
| 0.0.27 | 1 / 0 | |
| 0.0.26 | 1 / 0 | |
| 0.0.25 | 1 / 0 | |
| 0.0.24 | 1 / 0 | |
| 0.0.23 | 1 / 0 | |
| 0.0.22 | 1 / 0 | |
| 0.0.21 | 1 / 0 | |
| 0.0.20 | 1 / 0 | |
| 0.0.19 | 1 / 0 | |
| 0.0.18 | 1 / 0 | |
| 0.0.17 | 1 / 0 | |
| 0.0.16 | 1 / 0 | |
| 0.0.15 | 1 / 0 | |
| 0.0.14 | 1 / 0 | |
| 0.0.13 | 1 / 0 | |
| 0.0.12 | 1 / 0 | |
| 0.0.11 | 1 / 0 | |
| 0.0.10 | 1 / 0 | |
| 0.0.9 | 1 / 0 | |
| 0.0.8 | 1 / 0 | |
| 0.0.7 | 1 / 0 | |
| 0.0.6 | 1 / 0 | |
| 0.0.5 | 1 / 0 | |
| 0.0.4 | 1 / 0 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 1 / 0 |
v0.0.94
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.93
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.92
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.91
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.90
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.89
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.88
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.87
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.84
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.83
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.80
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.