@docusaurus/plugin-google-gtag
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:tslib | AI (phantom-deps): Known implicit runtime dep pattern for TypeScript-compiled packages; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/gtag.js | AI (phantom-deps): Type-only package loaded by convention in TS projects; not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@docusaurus/core | AI (phantom-deps): Same-org peer dep; standard pattern for Docusaurus plugin packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 5 / 0 | |
| 3.10.0 | 5 / 0 | |
| 3.9.2 | 5 / 0 | |
| 3.9.1 | 5 / 0 | |
| 3.9.0 | 5 / 0 | |
| 3.8.1 | 5 / 0 | |
| 3.8.0 | 5 / 0 |
v3.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.