← Home

@tryghost/mg-mailchimp-members

Converts a Mailchimp members `csv` export and generates a `csv` file you can import into a Ghost installation.

36
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 publisher-changed AI (provenance): TryGhost org migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this package going forward. ai
provenance missing-githead AI (provenance): SLSA provenance attestation present; missing gitHead is a cosmetic metadata gap, not a supply chain risk for this package. ai
phantom-deps phantom-dep:@tryghost/debug AI (phantom-deps): Same-org Ghost package; phantom-dep heuristic unreliable for transitive/indirect usage within monorepo. ai
phantom-deps phantom-dep:@tryghost/errors AI (phantom-deps): Same-org Ghost package; phantom-dep heuristic unreliable for transitive/indirect usage within monorepo. ai
dependencies unvetted-dep:@tryghost/mg-fs-utils AI (dependencies): Same Ghost Foundation monorepo dependency; stable false positive for this package family. ai

Versions (showing 36 of 36)

Version Deps Published
0.14.2 1 / 5
0.14.1 1 / 5
0.14.0 1 / 5
0.13.0 1 / 5
0.12.0 1 / 5
0.11.3 1 / 5
0.11.2 1 / 5
0.11.1 3 / 8
0.11.0 3 / 8
0.10.0 3 / 8
0.9.0 3 / 8
0.8.0 3 / 8
0.7.0 3 / 8
0.6.0 3 / 8
0.5.0 3 / 7
0.4.30 3 / 7
0.4.29 3 / 7
0.4.28 3 / 9
0.4.27 3 / 9
0.4.26 3 / 9
0.4.25 3 / 9
0.4.24 3 / 9
0.4.23 3 / 9
0.4.22 3 / 9
0.4.21 3 / 9
0.4.20 3 / 9
0.4.19 3 / 9
0.4.18 3 / 9
0.4.17 3 / 9
0.4.16 3 / 9
0.4.15 3 / 9
0.4.14 3 / 9
0.4.13 3 / 9
0.4.12 3 / 9
0.4.11 3 / 9
0.4.10 3 / 9

v0.14.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.14.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.14.0

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.4.20

1 finding
LOW No provenance attestation provenance

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

v0.4.19

1 finding
LOW No provenance attestation provenance

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

v0.4.18

1 finding
LOW No provenance attestation provenance

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

v0.4.17

1 finding
LOW No provenance attestation provenance

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

v0.4.16

1 finding
LOW No provenance attestation provenance

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

v0.4.15

1 finding
LOW No provenance attestation provenance

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

v0.4.14

1 finding
LOW No provenance attestation provenance

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

v0.4.13

1 finding
LOW No provenance attestation provenance

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

v0.4.12

1 finding
LOW No provenance attestation provenance

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

v0.4.11

1 finding
LOW No provenance attestation provenance

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

v0.4.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.