@backstage-community/plugin-analytics-provider-segment
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): Standard MUI v4 alpha package; pinned version is the canonical one used across Backstage plugins. | ai | |
| dependencies | unvetted-dep:@segment/analytics-next | AI (dependencies): Official Segment analytics SDK; expected core dependency for this analytics provider plugin. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Backstage plugin pattern; declared for config/peer use. | ai | |
| phantom-deps | phantom-dep:@material-ui/lab | AI (phantom-deps): Backstage plugin pattern; MUI deps declared for config/peer use. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Backstage plugin pattern; deps declared for peer/config use, not direct import. | ai | |
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): Backstage plugin pattern; MUI deps declared for config/peer use. | ai | |
| phantom-deps | phantom-dep:@material-ui/icons | AI (phantom-deps): Backstage plugin pattern; MUI deps declared for config/peer use. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Legitimate community plugin; missing description is cosmetic and stable across versions. | ai | |
| phantom-deps | phantom-dep:@backstage/core-components | AI (phantom-deps): Backstage plugin config-file reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/theme | AI (phantom-deps): Backstage plugin config-file reference pattern; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.28.0 | 7 / 13 | |
| 1.27.0 | 7 / 13 | |
| 1.26.0 | 6 / 13 | |
| 1.25.1 | 6 / 13 | |
| 1.25.0 | 11 / 15 | |
| 1.24.0 | 11 / 15 | |
| 1.23.0 | 11 / 15 | |
| 1.22.2 | 11 / 15 | |
| 1.22.1 | 11 / 15 | |
| 1.22.0 | 11 / 15 | |
| 1.21.0 | 11 / 15 | |
| 1.16.0 | 10 / 16 | |
| 1.15.0 | 10 / 16 |
v1.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.