@tryghost/mw-error-handler
Express middleware utilities for normalizing and rendering Ghost API errors
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 | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence reflects CI environment change, not a supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Ghost Foundation package; lack of provenance is common and not a risk here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Ghost Foundation middleware package; sparse metadata is expected for scoped org packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentional for this internal Ghost scoped package; stable across versions. | ai | |
| dependencies | unvetted-dep:@tryghost/tpl | AI (dependencies): Internal Ghost Foundation dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@tryghost/debug | AI (dependencies): Internal Ghost Foundation dependency; expected for this package family. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.2.3 | 6 / 1 | |
| 3.2.2 | 6 / 1 | |
| 3.2.1 | 6 / 1 | |
| 3.2.0 | 6 / 1 | |
| 3.1.0 | 6 / 1 | |
| 3.0.3 | 6 / 1 | |
| 3.0.2 | 6 / 1 | |
| 3.0.1 | 6 / 1 | |
| 3.0.0 | 6 / 3 | |
| 2.2.1 | 6 / 3 | |
| 2.2.0 | 6 / 3 | |
| 2.1.0 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.0.13 | 6 / 3 | |
| 1.0.12 | 6 / 3 | |
| 1.0.11 | 6 / 3 | |
| 1.0.10 | 6 / 3 | |
| 1.0.9 | 6 / 3 | |
| 1.0.8 | 6 / 3 |
v3.2.3
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.
v3.2.2
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.
v3.2.1
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.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.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.