@tryghost/kg-default-nodes
Lexical node definitions for the default nodes used in Ghost's Koenig editor
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Ghost Foundation org package published via GitHub Actions CI/CD with SLSA provenance; maintainer additions are routine org management. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; dormancy explained by active Ghost org development cycle. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Ghost monorepo package; missing description is a known pattern, not a malware signal. | ai | |
| dependencies | unvetted-dep:html-minifier | AI (dependencies): html-minifier 4.0.0 is a well-known, stable utility; no known malicious activity; stable for this package. | ai | |
| phantom-deps | phantom-dep:jsdom | AI (phantom-deps): jsdom is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lexical/selection | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-minifier | AI (phantom-deps): html-minifier is declared in both deps and devDeps; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@lexical/utils | AI (phantom-deps): Declared runtime dep; used transitively via lexical ecosystem — stable false positive. | ai | |
| phantom-deps | phantom-dep:@lexical/clipboard | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 12 / 20 | |
| 2.1.1 | 12 / 20 | |
| 2.1.0 | 12 / 20 | |
| 2.0.21 | 12 / 15 | |
| 2.0.20 | 12 / 15 | |
| 2.0.19 | 12 / 15 | |
| 2.0.16 | 12 / 15 | |
| 2.0.15 | 12 / 14 | |
| 2.0.14 | 12 / 14 | |
| 2.0.13 | 12 / 14 | |
| 2.0.12 | 12 / 14 | |
| 2.0.11 | 12 / 14 | |
| 2.0.10 | 12 / 14 | |
| 2.0.8 | 12 / 14 | |
| 2.0.7 | 12 / 14 | |
| 2.0.6 | 12 / 14 | |
| 2.0.5 | 12 / 14 | |
| 2.0.4 | 12 / 14 | |
| 2.0.1 | 12 / 14 | |
| 2.0.0 | 7 / 14 |
v2.1.2
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.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.