@tryghost/mg-libsyn
Migrate content from Libsyn using your sites RSS feed, and generate 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:xml2json | AI (dependencies): xml2json is a standard XML parsing library used legitimately in this Ghost migration tool; no malicious indicators. | ai | |
| provenance | slsa-provenance | AI (provenance): Ghost Foundation publishes via CI/CD with Sigstore attestation; stable 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 |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.11.2 | 5 / 1 | |
| 0.11.1 | 5 / 1 | |
| 0.11.0 | 5 / 1 | |
| 0.10.0 | 5 / 1 | |
| 0.9.0 | 6 / 1 | |
| 0.8.3 | 6 / 1 | |
| 0.8.2 | 6 / 1 | |
| 0.8.1 | 6 / 1 | |
| 0.8.0 | 6 / 1 | |
| 0.7.0 | 6 / 1 | |
| 0.6.0 | 6 / 1 | |
| 0.5.0 | 7 / 1 | |
| 0.4.0 | 7 / 1 | |
| 0.3.0 | 7 / 1 | |
| 0.2.0 | 7 / 1 | |
| 0.1.27 | 7 / 3 | |
| 0.1.25 | 7 / 3 | |
| 0.1.23 | 7 / 3 | |
| 0.1.22 | 7 / 3 | |
| 0.1.21 | 7 / 3 | |
| 0.1.20 | 7 / 3 | |
| 0.1.19 | 7 / 3 | |
| 0.1.18 | 7 / 3 | |
| 0.1.17 | 7 / 3 | |
| 0.1.16 | 7 / 3 |
v0.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.