gscan
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used for git version detection in ghost-version.js; stable CLI tool pattern for this package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dep used by the app server; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:multer | AI (phantom-deps): multer is a declared runtime dep used via config; phantom-dep is a false positive. | ai | |
| phantom-deps | phantom-dep:@sentry/node | AI (phantom-deps): Declared runtime dep used via config/server setup; false positive. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads check modules from a fixed local checksDir path; not user-controlled input. | ai | |
| phantom-deps | phantom-dep:@tryghost/server | AI (phantom-deps): First-party @tryghost dep used via config files; false positive. | ai | |
| phantom-deps | phantom-dep:@tryghost/logging | AI (phantom-deps): First-party @tryghost dep used via config files; false positive. | ai | |
| phantom-deps | phantom-dep:express-handlebars | AI (phantom-deps): Declared runtime dep used via config; false positive. | ai | |
| phantom-deps | phantom-dep:@tryghost/config | AI (phantom-deps): First-party @tryghost dep used via config files; false positive. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 18 / 9 | |
| 6.0.1 | 18 / 9 | |
| 6.0.0 | 17 / 9 | |
| 5.4.3 | 17 / 9 | |
| 5.4.2 | 18 / 9 | |
| 5.4.1 | 18 / 11 | |
| 5.4.0 | 18 / 11 | |
| 5.3.5 | 18 / 11 | |
| 5.3.4 | 18 / 11 | |
| 5.3.3 | 18 / 11 | |
| 5.3.2 | 18 / 11 | |
| 5.3.1 | 18 / 11 | |
| 5.3.0 | 18 / 11 | |
| 5.2.5 | 22 / 10 | |
| 5.2.4 | 22 / 10 |
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.