@instructure/ui-popover
A component for hiding or showing content based on user interaction.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Instructure monorepo publishes via GitHub Actions CI; individual maintainer removal is expected org practice. | ai | |
| dependencies | unvetted-dep:@instructure/ui-testable | AI (dependencies): Same-org Instructure UI package pinned to matching version; consistent with the rest of the dependency set. | ai | |
| dependencies | unvetted-dep:@instructure/ui-prop-types | AI (dependencies): Same-org Instructure UI package pinned to matching version; consistent with the rest of the dependency set. | ai | |
| phantom-deps | phantom-dep:@instructure/uid | AI (phantom-deps): Same-org sibling dep in a monorepo; phantom detection is a false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 15 / 7 | |
| 11.7.2 | 14 / 8 | |
| 11.7.1 | 14 / 8 | |
| 11.7.0 | 14 / 8 | |
| 11.6.0 | 14 / 8 | |
| 11.5.0 | 14 / 8 | |
| 11.4.0 | 14 / 8 | |
| 11.3.0 | 14 / 8 | |
| 11.2.0 | 14 / 8 | |
| 11.0.1 | 14 / 6 | |
| 11.0.0 | 14 / 6 | |
| 10.30.0 | 17 / 6 | |
| 10.29.0 | 17 / 6 | |
| 10.26.4 | 17 / 6 | |
| 10.26.3 | 17 / 6 |
v11.7.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.