@tryghost/sodo-search
- Run `pnpm` in Ghost monorepo root - Run `pnpm` in this directory
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Ghost Foundation uses automated CI/CD releases; rapid publishes are expected for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Ghost Foundation package; missing description is benign for internal/scoped packages. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is a minor pipeline change for this established Ghost org package. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a risk signal for established Ghost Foundation package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Ghost package; sparse README and missing keywords are typical for internal/specialized libraries, not spam indicators. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Ghost org package published via CI with SLSA provenance; maintainer additions are routine for this org. | ai | |
| phantom-deps | phantom-dep:@tryghost/content-api | AI (phantom-deps): Declared dependency; used in config context, stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@tryghost/i18n | AI (dependencies): Same org scope (TryGhost); workspace dependency, stable internal use. | ai | |
| dependencies | unvetted-dep:@tryghost/debug | AI (dependencies): Same org scope (TryGhost); stable internal dependency. | ai | |
| dependencies | unvetted-dep:flexsearch | AI (dependencies): flexsearch is a legitimate open-source search library; its use here is expected for a search component package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bundled UMB output; react is consumed at build time, not imported directly at runtime. | ai | |
| phantom-deps | phantom-dep:@tryghost/debug | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@tryghost/i18n | AI (phantom-deps): Same-org workspace dependency; phantom-dep heuristic is a stable false positive. | ai | |
| phantom-deps | phantom-dep:flexsearch | AI (phantom-deps): Build-time bundled dependency; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Same as react — build-time bundle dependency, not a runtime import. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.8.211 | 5 / 0 | |
| 1.8.207 | 5 / 0 | |
| 1.8.181 | 5 / 0 | |
| 1.8.176 | 5 / 0 | |
| 1.8.162 | 5 / 0 | |
| 1.8.83 | 5 / 20 | |
| 1.8.39 | 5 / 20 | |
| 1.8.37 | 5 / 20 | |
| 1.8.36 | 5 / 20 | |
| 1.8.20 | 5 / 13 | |
| 1.8.19 | 5 / 13 | |
| 1.8.18 | 5 / 13 | |
| 1.8.17 | 5 / 13 | |
| 1.8.16 | 5 / 12 | |
| 1.8.15 | 5 / 11 | |
| 1.8.14 | 5 / 11 | |
| 1.8.13 | 5 / 11 | |
| 1.8.12 | 5 / 11 | |
| 1.8.11 | 5 / 11 | |
| 1.8.9 | 4 / 9 | |
| 1.8.8 | 3 / 9 | |
| 1.8.7 | 3 / 9 | |
| 1.8.6 | 3 / 8 | |
| 1.8.5 | 3 / 8 | |
| 1.8.4 | 3 / 8 | |
| 1.8.3 | 3 / 8 | |
| 1.8.2 | 3 / 8 | |
| 1.8.1 | 3 / 8 | |
| 1.8.0 | 3 / 8 | |
| 1.7.0 | 4 / 8 | |
| 1.6.0 | 4 / 8 | |
| 1.5.6 | 4 / 8 | |
| 1.5.5 | 4 / 8 | |
| 1.5.4 | 4 / 8 | |
| 1.5.3 | 4 / 8 | |
| 1.5.2 | 4 / 8 | |
| 1.5.1 | 4 / 8 | |
| 1.5.0 | 4 / 8 | |
| 1.4.0 | 4 / 8 | |
| 1.3.0 | 4 / 8 | |
| 1.2.0 | 4 / 8 | |
| 1.1.1 | 4 / 7 |
v1.8.211
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.207
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.181
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.176
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.162
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.83
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.39
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.
v1.8.37
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.
v1.8.36
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.
v1.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (daniellockyer) than the most recent previously approved version (allouis) on 2025-03-13, but daniellockyer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (daniellockyer) than the most recent previously approved version (allouis) on 2025-02-10, but daniellockyer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (allouis) than the most recent previously approved version (9larsons) on 2025-02-06, but allouis is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.1
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: 9larsons.
This version was published by a different npm account (9larsons) than the most recent previously approved version (erisds) on 2024-11-15, but 9larsons is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (erisds) than the most recent previously approved version (9larsons) on 2024-10-31, but erisds is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (9larsons) than the most recent previously approved version (erisds) on 2024-10-03, but 9larsons is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.