@tryghost/mg-beehiiv
Converts a beehiiv `csv` export and generates a `zip` 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): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this package. | ai | |
| provenance | no-provenance | AI (provenance): Ghost Foundation monorepo package; no provenance is consistent across all versions of this package family. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Ghost org internal contributor addition; consistent with org's normal maintainer management pattern. | ai | |
| phantom-deps | phantom-dep:@tryghost/errors | AI (phantom-deps): Same org scope (@tryghost); stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@tryghost/debug | AI (phantom-deps): Same org scope (@tryghost); likely used transitively or conditionally within the package. | ai | |
| dependencies | unvetted-dep:@tryghost/mg-utils | AI (dependencies): Internal Ghost Foundation monorepo dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:simple-dom | AI (dependencies): Stable, pinned version used by Ghost ecosystem packages; no known issues. | ai | |
| dependencies | unvetted-dep:@tryghost/mg-fs-utils | AI (dependencies): Internal Ghost Foundation monorepo dependency; expected for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 6 / 5 | |
| 0.11.0 | 7 / 5 | |
| 0.10.3 | 7 / 5 | |
| 0.10.2 | 7 / 5 | |
| 0.10.1 | 9 / 9 | |
| 0.10.0 | 9 / 9 | |
| 0.9.0 | 9 / 9 | |
| 0.8.0 | 8 / 9 | |
| 0.7.0 | 8 / 9 | |
| 0.6.0 | 8 / 9 | |
| 0.5.0 | 8 / 9 | |
| 0.4.0 | 8 / 8 | |
| 0.3.16 | 8 / 8 | |
| 0.3.15 | 8 / 8 | |
| 0.3.14 | 8 / 10 | |
| 0.3.13 | 8 / 10 | |
| 0.3.12 | 8 / 10 | |
| 0.3.11 | 8 / 10 | |
| 0.3.10 | 8 / 10 | |
| 0.3.9 | 8 / 10 | |
| 0.3.8 | 8 / 10 |
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.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
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.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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.