@motech-development/breeze-ui
Breeze UI component library
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Likely used in bundled dist build, not scannable by heuristic. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Likely used in bundled dist build, not scannable by heuristic. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Peer dep of react-popper; referenced in config, not directly imported — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Peer dep of react-fontawesome; config-referenced only — stable false positive for this package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 7 / 30 | |
| 3.0.2 | 7 / 30 | |
| 3.0.1 | 7 / 30 | |
| 3.0.0 | 7 / 30 | |
| 2.4.0 | 15 / 48 | |
| 2.3.1 | 15 / 48 | |
| 2.3.0 | 15 / 49 | |
| 2.2.0 | 15 / 50 | |
| 2.1.9 | 15 / 49 | |
| 2.1.8 | 15 / 49 | |
| 2.1.7 | 15 / 49 | |
| 2.1.6 | 15 / 49 | |
| 2.1.5 | 15 / 49 | |
| 2.1.4 | 15 / 49 | |
| 2.1.3 | 15 / 49 | |
| 2.1.2 | 15 / 49 | |
| 2.1.1 | 15 / 49 | |
| 2.1.0 | 15 / 49 | |
| 2.0.34 | 15 / 49 | |
| 2.0.33 | 15 / 49 | |
| 2.0.32 | 15 / 49 | |
| 2.0.31 | 15 / 49 | |
| 2.0.30 | 15 / 50 | |
| 2.0.29 | 15 / 50 | |
| 2.0.28 | 15 / 49 | |
| 2.0.27 | 15 / 47 | |
| 2.0.26 | 15 / 47 | |
| 2.0.25 | 15 / 47 | |
| 2.0.24 | 15 / 47 | |
| 2.0.23 | 15 / 47 | |
| 2.0.22 | 15 / 47 | |
| 2.0.21 | 15 / 47 | |
| 2.0.20 | 15 / 47 | |
| 2.0.19 | 15 / 47 | |
| 2.0.18 | 15 / 47 | |
| 2.0.17 | 15 / 47 | |
| 2.0.16 | 15 / 47 | |
| 2.0.15 | 15 / 47 | |
| 2.0.14 | 15 / 46 | |
| 2.0.13 | 15 / 46 | |
| 2.0.12 | 15 / 46 | |
| 2.0.11 | 15 / 46 | |
| 2.0.10 | 15 / 46 | |
| 2.0.9 | 15 / 46 | |
| 2.0.8 | 15 / 46 | |
| 2.0.7 | 15 / 46 | |
| 2.0.6 | 15 / 46 | |
| 2.0.5 | 15 / 46 | |
| 2.0.4 | 15 / 46 | |
| 2.0.3 | 15 / 46 | |
| 2.0.2 | 15 / 46 |
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.