← Home

@tryghost/mg-jekyll-export

npm Repository Homepage

tbc

24
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): SLSA provenance attestation present; gitHead absence is a minor metadata gap, not a supply chain risk for this package. ai
publish-pattern dormant-publish AI (publish-pattern): Ghost Foundation monorepo; infrequent releases are normal for migration utility packages. ai
dependencies unvetted-dep:markdown-it AI (dependencies): Well-known markdown parser; stable dependency for this Ghost migration tool. ai
dependencies unvetted-dep:@tryghost/mg-utils AI (dependencies): First-party Ghost org dependency; stable for this package. ai
dependencies unvetted-dep:@tryghost/pretty-cli AI (dependencies): First-party Ghost org dependency; stable for this package. ai
dependencies unvetted-dep:@tryghost/mg-fs-utils AI (dependencies): First-party Ghost org dependency; stable for this package. ai

Versions (showing 24 of 24)

Version Deps Published
0.13.2 7 / 1
0.13.1 7 / 1
0.13.0 7 / 1
0.12.0 7 / 1
0.11.0 7 / 1
0.10.3 7 / 1
0.10.0 7 / 1
0.8.0 7 / 1
0.7.0 6 / 1
0.5.0 6 / 1
0.3.43 6 / 1
0.3.39 6 / 3
0.3.38 6 / 3
0.3.36 6 / 3
0.3.35 6 / 3
0.3.34 6 / 3
0.3.33 6 / 3
0.3.32 6 / 3
0.3.31 6 / 3
0.3.30 6 / 3
0.3.29 6 / 3
0.3.28 6 / 3
0.3.27 6 / 3
0.3.26 6 / 3

v0.13.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.13.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.3.34

1 finding
LOW No provenance attestation provenance

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

v0.3.33

1 finding
LOW No provenance attestation provenance

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

v0.3.32

1 finding
LOW No provenance attestation provenance

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

v0.3.31

1 finding
LOW No provenance attestation provenance

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

v0.3.30

1 finding
LOW No provenance attestation provenance

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

v0.3.29

1 finding
LOW No provenance attestation provenance

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

v0.3.28

1 finding
LOW No provenance attestation provenance

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

v0.3.27

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.

v0.3.26

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.