@tryghost/mg-beehiiv-members
Converts a beehiiv members `csv` 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package now uses SLSA provenance attestation via GitHub Actions; gitHead is superseded by Sigstore attestation. | ai | |
| provenance | no-provenance | AI (provenance): Ghost Foundation packages consistently lack provenance; stable false positive for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Ghost org migration utility; missing description is cosmetic, not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@tryghost/debug | AI (phantom-deps): Same-org dep; may be used transitively or conditionally — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tryghost/errors | AI (phantom-deps): Same-org dep; stable false positive for this Ghost Foundation package. | ai | |
| dependencies | unvetted-dep:@tryghost/mg-fs-utils | AI (dependencies): Same Ghost Foundation monorepo package; stable false positive for this package family. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 2 / 5 | |
| 0.8.3 | 2 / 5 | |
| 0.8.2 | 2 / 5 | |
| 0.8.1 | 4 / 8 | |
| 0.8.0 | 4 / 8 | |
| 0.7.0 | 4 / 8 | |
| 0.6.0 | 4 / 8 | |
| 0.5.0 | 4 / 8 | |
| 0.4.0 | 4 / 8 | |
| 0.3.0 | 4 / 8 | |
| 0.2.0 | 4 / 7 | |
| 0.1.25 | 4 / 7 | |
| 0.1.24 | 4 / 7 | |
| 0.1.23 | 4 / 9 | |
| 0.1.22 | 4 / 9 | |
| 0.1.21 | 4 / 9 | |
| 0.1.20 | 4 / 9 | |
| 0.1.19 | 3 / 9 | |
| 0.1.18 | 3 / 9 | |
| 0.1.17 | 3 / 9 |
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.