@tryghost/mg-stripe
Migrate Stripe products, prices, coupons, subscriptions and invoices from an old to a new Stripe account.
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:@tryghost/debug | AI (dependencies): Same org scope (@tryghost); consistent across versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Ghost org internal tooling package; missing description is a cosmetic issue, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Ghost Foundation monorepo package; no provenance is consistent across all their packages. | ai | |
| phantom-deps | phantom-dep:sywac | AI (phantom-deps): CLI framework declared as dep; used in CLI config files, not directly imported in main source. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Declared dep used in CLI config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tryghost/debug | AI (phantom-deps): Same-org Ghost Foundation package; likely used transitively or in build tooling. | ai | |
| phantom-deps | phantom-dep:@tryghost/errors | AI (phantom-deps): Same-org Ghost Foundation package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@tryghost/pretty-cli | AI (dependencies): First-party Ghost Foundation package; stable false positive for this package family. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 7 / 8 | |
| 0.9.3 | 7 / 8 | |
| 0.9.2 | 7 / 8 | |
| 0.9.1 | 13 / 10 | |
| 0.9.0 | 13 / 10 | |
| 0.8.0 | 13 / 10 | |
| 0.7.0 | 13 / 10 | |
| 0.6.0 | 13 / 10 | |
| 0.5.0 | 13 / 10 | |
| 0.4.0 | 13 / 10 | |
| 0.3.0 | 13 / 9 | |
| 0.2.22 | 13 / 9 | |
| 0.2.21 | 13 / 9 | |
| 0.2.20 | 13 / 12 | |
| 0.2.19 | 13 / 12 | |
| 0.2.18 | 13 / 12 | |
| 0.2.17 | 13 / 12 | |
| 0.2.16 | 13 / 12 | |
| 0.2.15 | 13 / 12 | |
| 0.2.14 | 13 / 12 | |
| 0.2.13 | 13 / 12 | |
| 0.2.12 | 13 / 12 | |
| 0.2.11 | 13 / 12 |
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.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.9.1
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
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
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.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.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
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.2.19
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.2.18
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.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
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.2.13
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.2.12
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.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.