@tryghost/mg-medium-members
Converts a Medium members `txt` export and generates a `csv` file you can import into a Ghost installation.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tryghost/debug | AI (phantom-deps): Same-org Ghost dependency; declared in package.json, likely used transitively or indirectly within the build. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 1 / 5 | |
| 0.9.2 | 1 / 5 | |
| 0.4.0 | 2 / 8 | |
| 0.3.0 | 2 / 7 | |
| 0.2.21 | 2 / 7 | |
| 0.2.20 | 2 / 7 | |
| 0.2.19 | 2 / 9 | |
| 0.2.18 | 2 / 9 | |
| 0.2.17 | 2 / 9 | |
| 0.2.16 | 2 / 9 | |
| 0.2.15 | 2 / 9 |
v0.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.