@nuxtjs/shopify
Easily integrate Shopify with Nuxt 3 and 4 🚀
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation under nuxt-modules org; legitimate automation pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-level CI/CD takeover of publishing; nuxt-modules org package with SLSA provenance. | ai | |
| dependencies | unvetted-dep:@shopify/graphql-codegen | AI (dependencies): Official Shopify codegen package; expected dependency for this module. | ai | |
| dependencies | unvetted-dep:@shopify/graphql-client | AI (dependencies): Official Shopify SDK package; stable dependency for this Shopify integration module. | ai | |
| dependencies | unvetted-dep:@shopify/api-codegen-preset | AI (dependencies): Official Shopify codegen preset; expected for this Shopify Nuxt module. | ai | |
| dependencies | unvetted-dep:@graphql-codegen/import-types-preset | AI (dependencies): Well-known graphql-codegen ecosystem package; stable for this module. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/plugin-helpers | AI (phantom-deps): Config-file-only reference; expected codegen tooling pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/import-types-preset | AI (phantom-deps): Config-file-only reference; expected codegen tooling pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/introspection | AI (phantom-deps): Config-file-only reference; expected codegen tooling pattern. | ai | |
| phantom-deps | phantom-dep:@shopify/api-codegen-preset | AI (phantom-deps): Config-file-only reference; not a runtime import, expected for codegen tooling. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 23 / 19 | |
| 0.5.3 | 23 / 19 | |
| 0.5.2 | 23 / 19 | |
| 0.5.1 | 23 / 19 | |
| 0.5.0 | 23 / 19 | |
| 0.4.6 | 23 / 17 | |
| 0.4.5 | 23 / 17 | |
| 0.4.4 | 23 / 16 | |
| 0.4.3 | 23 / 16 | |
| 0.4.2 | 23 / 16 | |
| 0.4.1 | 23 / 16 | |
| 0.4.0 | 23 / 16 | |
| 0.3.16 | 21 / 17 | |
| 0.3.15 | 21 / 17 | |
| 0.3.14 | 19 / 17 | |
| 0.3.13 | 20 / 17 | |
| 0.3.12 | 20 / 17 | |
| 0.3.11 | 20 / 17 | |
| 0.3.10 | 20 / 17 | |
| 0.3.9 | 19 / 18 | |
| 0.3.8 | 19 / 18 | |
| 0.3.7 | 19 / 18 | |
| 0.3.6 | 19 / 18 | |
| 0.3.5 | 19 / 18 | |
| 0.3.4 | 19 / 18 | |
| 0.3.3 | 19 / 18 | |
| 0.3.2 | 18 / 18 | |
| 0.3.1 | 18 / 18 | |
| 0.3.0 | 18 / 18 | |
| 0.2.0 | 14 / 17 | |
| 0.1.7 | 14 / 17 | |
| 0.1.6 | 14 / 17 | |
| 0.1.5 | 14 / 18 |
v0.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
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.6
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.
Published 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 was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.16
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.15
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.14
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.13
2 findingsThis version was published by a different npm account than previous versions on 2026-01-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.12
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.11
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.9
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.8
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
2 findingsThis version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
2 findingsThis version was published by a different npm account than previous versions on 2025-11-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
2 findingsThis version was published by a different npm account than previous versions on 2025-11-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
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 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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.