@backstage-community/plugin-analytics-module-ga4
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Backstage community plugin; description omission is a known pattern in this monorepo, not a malware indicator. | ai | |
| dependencies | unvetted-dep:react-ga4 | AI (dependencies): react-ga4 is the canonical GA4 React wrapper; expected dependency for a GA4 analytics plugin. | ai | |
| phantom-deps | phantom-dep:@backstage/core-components | AI (phantom-deps): @backstage/core-components is a declared runtime dep; phantom-dep heuristic fires due to config-file-only reference pattern common in Backstage plugins. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.21.0 | 6 / 11 | |
| 0.20.0 | 6 / 11 | |
| 0.19.1 | 6 / 11 | |
| 0.19.0 | 6 / 11 | |
| 0.18.0 | 6 / 11 | |
| 0.17.0 | 5 / 11 | |
| 0.16.2 | 5 / 11 | |
| 0.16.1 | 5 / 11 | |
| 0.16.0 | 5 / 11 | |
| 0.15.0 | 5 / 11 | |
| 0.14.0 | 5 / 11 | |
| 0.13.0 | 5 / 11 | |
| 0.12.0 | 5 / 11 | |
| 0.11.0 | 5 / 11 | |
| 0.10.0 | 5 / 11 | |
| 0.9.0 | 5 / 11 | |
| 0.8.0 | 5 / 11 | |
| 0.7.0 | 5 / 11 | |
| 0.6.1 | 5 / 11 | |
| 0.6.0 | 5 / 12 | |
| 0.5.0 | 5 / 12 | |
| 0.4.0 | 5 / 12 | |
| 0.3.0 | 5 / 12 | |
| 0.2.11 | 5 / 12 | |
| 0.2.10 | 5 / 12 | |
| 0.2.9 | 5 / 12 | |
| 0.2.8 | 5 / 12 | |
| 0.2.7 | 5 / 12 | |
| 0.2.6 | 5 / 12 | |
| 0.2.5 | 5 / 12 |
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.