@posthog/nuxt
Nuxt module for Posthog 🦔
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): @posthog/nuxt is a legitimate PostHog-org Nuxt module; Levenshtein match to 'next' is coincidental. | ai | |
| phantom-deps | phantom-dep:@posthog/cli | AI (phantom-deps): Same org scope; @posthog/cli is a build-time tool dependency, not a runtime import. | ai |
Versions (showing 82 of 283)
| Version | Deps | Published |
|---|---|---|
| 1.4.31 | 5 / 7 | |
| 1.4.30 | 5 / 7 | |
| 1.4.29 | 5 / 7 | |
| 1.4.28 | 5 / 7 | |
| 1.4.27 | 5 / 7 | |
| 1.4.26 | 5 / 7 | |
| 1.4.25 | 5 / 7 | |
| 1.4.24 | 5 / 7 | |
| 1.4.23 | 5 / 7 | |
| 1.4.22 | 5 / 7 | |
| 1.4.21 | 5 / 7 | |
| 1.4.20 | 5 / 7 | |
| 1.4.19 | 5 / 7 | |
| 1.4.18 | 5 / 7 | |
| 1.4.17 | 5 / 7 | |
| 1.4.16 | 5 / 7 | |
| 1.4.15 | 5 / 7 | |
| 1.4.14 | 5 / 7 | |
| 1.4.13 | 5 / 7 | |
| 1.4.12 | 5 / 7 | |
| 1.4.11 | 5 / 7 | |
| 1.4.10 | 5 / 7 | |
| 1.4.9 | 5 / 7 | |
| 1.4.8 | 5 / 7 | |
| 1.4.7 | 5 / 7 | |
| 1.4.6 | 5 / 7 | |
| 1.4.5 | 5 / 7 | |
| 1.4.4 | 5 / 7 | |
| 1.4.3 | 5 / 7 | |
| 1.4.2 | 5 / 7 | |
| 1.4.1 | 5 / 7 | |
| 1.4.0 | 5 / 7 | |
| 1.3.25 | 5 / 7 | |
| 1.3.24 | 5 / 7 | |
| 1.3.23 | 5 / 7 | |
| 1.3.22 | 5 / 7 | |
| 1.3.21 | 5 / 7 | |
| 1.3.20 | 5 / 7 | |
| 1.3.19 | 5 / 7 | |
| 1.3.18 | 5 / 7 | |
| 1.3.17 | 5 / 7 | |
| 1.3.16 | 5 / 7 | |
| 1.3.15 | 5 / 7 | |
| 1.3.14 | 5 / 7 | |
| 1.3.13 | 5 / 7 | |
| 1.3.12 | 5 / 7 | |
| 1.3.11 | 5 / 7 | |
| 1.3.10 | 5 / 7 | |
| 1.3.9 | 5 / 7 | |
| 1.3.8 | 5 / 7 | |
| 1.3.7 | 5 / 7 | |
| 1.3.6 | 5 / 7 | |
| 1.3.5 | 5 / 7 | |
| 1.3.4 | 5 / 7 | |
| 1.3.3 | 5 / 7 | |
| 1.3.2 | 5 / 7 | |
| 1.3.1 | 5 / 7 | |
| 1.3.0 | 5 / 7 | |
| 1.2.10 | 5 / 7 | |
| 1.2.8 | 5 / 7 | |
| 1.2.7 | 5 / 7 | |
| 1.2.6 | 5 / 7 | |
| 1.2.5 | 5 / 7 | |
| 1.2.4 | 5 / 7 | |
| 1.2.3 | 5 / 7 | |
| 1.2.2 | 5 / 7 | |
| 1.2.1 | 5 / 7 | |
| 1.2.0 | 5 / 7 | |
| 1.1.5 | 5 / 7 | |
| 1.1.4 | 5 / 7 | |
| 1.1.3 | 5 / 7 | |
| 1.1.2 | 5 / 7 | |
| 1.1.1 | 5 / 7 | |
| 1.1.0 | 5 / 7 | |
| 1.0.3 | 5 / 7 | |
| 1.0.2 | 5 / 7 | |
| 1.0.1 | 5 / 7 | |
| 1.0.0 | 5 / 7 | |
| 0.0.27 | 5 / 7 | |
| 0.0.26 | 5 / 7 | |
| 0.0.25 | 5 / 7 | |
| 0.0.24 | 5 / 7 |
v1.4.31
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.30
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.29
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.28
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.27
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.26
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.25
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.24
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.23
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.22
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.21
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.20
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.19
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.18
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.17
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.16
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.15
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.14
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.13
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.12
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.11
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.10
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.9
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.8
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.7
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.6
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.5
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.4
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.3
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.2
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.1
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.25
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.24
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.23
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.22
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.21
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.20
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.19
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.18
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.17
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.16
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.15
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.14
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.13
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.12
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.11
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.10
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.9
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.8
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.7
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.5
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.4
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.3
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.2
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
2 findingsPackage name '@posthog/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.