← Home

@tryghost/mg-html-lexical

npm Repository Homepage

A little wrapper tool for migrating all HTML fields of posts to Lexical

39
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

zimoatghostallouiskernalghostchrisraibleerisdsjohnonolankevinansfieldcobbspuraileencgnjlohminimaluminiumsam-lordpauladamdavisbobvaneckjoeegrigghadretjonhickmanerik-ghostsagzyvershwalzach1618mike182ukluissazevedolsingernickmoretonrenatoworksrblstr-ghostevanhahn-ghostweylandswartghost-slimertmciescojonatan-ghost9larsons

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Absence of gitHead is expected after switch to GitHub Actions publish flow; SLSA attestation provides stronger provenance. ai
provenance publisher-changed AI (provenance): TryGhost migrated to GitHub Actions CI/CD publishing with SLSA attestation; this is a legitimate org-wide transition. ai

Versions (showing 39 of 39)

Version Deps Published
0.10.2 2 / 6
0.10.1 2 / 6
0.10.0 2 / 6
0.9.0 2 / 6
0.8.0 2 / 6
0.7.3 2 / 6
0.7.2 2 / 6
0.7.1 2 / 9
0.7.0 2 / 9
0.6.0 2 / 9
0.5.0 2 / 9
0.4.0 2 / 9
0.3.0 2 / 9
0.2.0 2 / 9
0.1.0 2 / 8
0.0.33 2 / 8
0.0.32 2 / 8
0.0.31 2 / 10
0.0.30 2 / 10
0.0.29 2 / 10
0.0.28 2 / 10
0.0.27 2 / 10
0.0.26 2 / 10
0.0.25 2 / 10
0.0.24 2 / 10
0.0.23 2 / 10
0.0.22 2 / 10
0.0.21 2 / 10
0.0.20 2 / 10
0.0.19 2 / 10
0.0.18 2 / 10
0.0.17 2 / 10
0.0.16 2 / 10
0.0.15 2 / 10
0.0.14 2 / 10
0.0.13 2 / 10
0.0.12 2 / 10
0.0.11 2 / 10
0.0.10 2 / 10

v0.10.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.10.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.