@chakra-ui/media-query
A React hook for changing properties or visibility of a component based on css media query
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are official @chakra-ui sibling packages replacing removed @chakra-ui/utils. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo lockstep release pattern from long-trusted publisher, not account takeover. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/utils | AI (phantom-deps): Same-org monorepo dep, used indirectly via workspace build. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/react-env | AI (phantom-deps): Same-org monorepo dep, used indirectly via workspace build. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Monorepo publish/build variance, not a stub replacement given trusted publisher. | ai | |
| provenance | no-provenance | AI (provenance): Chakra UI monorepo packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 3 / 8 | |
| 3.2.12 | 3 / 8 | |
| 3.2.11 | 3 / 8 | |
| 3.2.2 | 2 / 8 | |
| 3.2.1 | 2 / 8 | |
| 3.2.0 | 2 / 5 | |
| 3.1.2 | 2 / 5 | |
| 3.1.0 | 2 / 5 | |
| 3.0.2 | 2 / 5 | |
| 3.0.1 | 2 / 5 | |
| 3.0.0 | 2 / 5 |
v3.2.11
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: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
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: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
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: segunadebayo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.