@md-oss/analytics
Next.js analytics helpers with Vercel Analytics + optional Google Analytics
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): React types loaded by convention in Next.js packages; stable pattern. | ai | |
| phantom-deps | phantom-dep:@md-oss/config | AI (phantom-deps): Internal org dependency; same-scope pattern in monorepo. | ai | |
| dependencies | unvetted-dep:@t3-oss/env-nextjs | AI (dependencies): Well-known T3 ecosystem package; stable false positive for this analytics helper. | ai | |
| dependencies | unvetted-dep:@next/third-parties | AI (dependencies): Official Next.js first-party package; stable false positive for this analytics helper. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 5 / 4 | |
| 0.7.0 | 5 / 4 | |
| 0.3.9 | 7 / 3 | |
| 0.3.8 | 7 / 3 | |
| 0.3.6 | 7 / 3 | |
| 0.3.5 | 7 / 3 | |
| 0.2.1 | 7 / 3 | |
| 0.2.0 | 7 / 3 | |
| 0.1.7 | 7 / 3 | |
| 0.1.6 | 7 / 3 | |
| 0.1.5 | 7 / 3 | |
| 0.1.2 | 7 / 3 | |
| 0.1.0 | 7 / 3 |
v0.7.1
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.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.8
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.