@tryghost/content-api
JavaScript Client Library for the Ghost [Content API](https://ghost.org/docs/content-api/)
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-stale | AI (provenance): Old, long-stable publisher change (2022) for established Ghost SDK package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Explained by bundler/polyfill dependency changes across many skipped versions. | ai | |
| phantom-deps | phantom-dep:ghost-ignition | AI (phantom-deps): Legitimate Ghost dependency, likely used in build output not scanned source. | ai | |
| dependencies | unvetted-dep:ghost-ignition | AI (dependencies): First-party Ghost ecosystem logging package, not a supply-chain risk. | ai | |
| source-diff | net-exec-file-transition:umd/content-api.min.js | AI (source-diff): Minified bundle output of same polyfill code, not malicious. | ai | |
| source-diff | net-exec-file-transition:es/content-api.js | AI (source-diff): Bundled core-js/axios polyfill code from rollup build, not an injected dropper. | ai | |
| provenance | publisher-changed | AI (provenance): Ghost Foundation migrated to GitHub Actions CI publishing; SLSA attestation confirms supply chain integrity. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal paired with org-level maintainer rotation; no malicious indicators present. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are ghost-org accounts consistent with org-level team rotation. | ai |
Versions (showing 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 2 / 14 | |
| 1.3.3 | 2 / 14 | |
| 1.3.2 | 2 / 14 | |
| 1.3.1 | 2 / 14 | |
| 1.3.0 | 2 / 14 | |
| 1.2.13 | 2 / 13 | |
| 1.2.12 | 2 / 13 | |
| 1.2.11 | 2 / 13 | |
| 1.2.10 | 2 / 13 | |
| 1.2.9 | 2 / 13 | |
| 1.2.8 | 2 / 13 | |
| 1.2.7 | 2 / 13 | |
| 1.2.6 | 2 / 13 | |
| 1.2.5 | 2 / 13 | |
| 1.2.4 | 2 / 13 | |
| 1.2.3 | 2 / 13 | |
| 1.2.2 | 2 / 13 | |
| 1.2.1 | 2 / 13 | |
| 1.2.0 | 2 / 13 | |
| 1.1.0 | 2 / 12 | |
| 1.0.0 | 2 / 12 |
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.