@vexip-ui/hooks
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from qmhc to GitHub Actions CI publishing is consistent with CI/CD migration; SLSA attestation confirms build integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established vexip-ui org package with SLSA provenance; dormancy followed by CI-published release with no code changes is low risk. | ai | |
| phantom-deps | phantom-dep:@vexip-ui/utils | AI (phantom-deps): Sibling monorepo package; declared as dependency and bundled into dist output rather than directly imported in source files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@juggle/resize-observer | AI (phantom-deps): Polyfill dependency referenced in config/build files rather than direct source imports; legitimate usage pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with long track record; lack of provenance is common and not a risk signal for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.9.4 | 3 / 1 | |
| 2.9.3 | 3 / 1 | |
| 2.9.2 | 3 / 1 | |
| 2.9.1 | 3 / 1 | |
| 2.9.0 | 3 / 1 | |
| 2.8.1 | 3 / 1 | |
| 2.8.0 | 3 / 1 | |
| 2.7.0 | 3 / 1 | |
| 2.6.0 | 3 / 1 | |
| 2.5.0 | 3 / 1 | |
| 2.4.1 | 3 / 1 | |
| 2.4.0 | 3 / 1 | |
| 2.3.1 | 3 / 1 | |
| 2.3.0 | 3 / 1 | |
| 2.2.3 | 3 / 1 | |
| 2.2.2 | 3 / 1 | |
| 2.2.1 | 3 / 1 | |
| 2.2.0 | 3 / 1 | |
| 2.1.1 | 3 / 1 | |
| 2.1.0 | 3 / 1 | |
| 2.0.2 | 3 / 1 | |
| 2.0.1 | 3 / 1 | |
| 2.0.0 | 3 / 1 |
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.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.
v2.5.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.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.