github.com/fluxcd/image-reflector-controller/api
The GitOps Toolkit container registry scanner
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 57
- Cadence
- ~27 days
- Last 12 months
- 12
Reach
- Stars
- 124
Details
- First release
- Dec 10, 2020
| Version | Released | |
|---|---|---|
v1.2.5
patch
|
v1.2.5
patch
Dependencies (4)
|
|
v1.2.4
patch
|
v1.2.4
patch
Dependencies (4)
|
|
v1.2.3
patch
|
v1.2.3
patch
Dependencies (4)
|
|
v1.2.2
patch
|
v1.2.2
patch
Dependencies (4)
|
|
v1.2.1
patch
|
v1.2.1
patch
Dependencies (4)
|
|
v1.2.0
minor
|
v1.2.0
minor
Dependencies (4)
|
|
v1.1.2
patch
|
v1.1.2
patch
Dependencies (4)
|
|
v1.1.1
patch
|
v1.1.1
patch
Dependencies (4)
|
|
v1.1.0
minor
|
v1.1.0
minor
Dependencies (4)
|
|
v1.0.4
patch
|
v1.0.4
patch
Dependencies (4)
|
|
v1.0.3
patch
|
v1.0.3
patch
Dependencies (4)
|
|
v1.0.2
patch
|
v1.0.2
patch
Dependencies (4)
|
|
v1.0.1
major
|
v1.0.1
major
Dependencies (4)
|
|
v1.0.0
major
|
v1.0.0
major
Dependencies (4)
|
|
v1.0.0-rc.1
pre
|
v1.0.0-rc.1
pre
Dependencies (4)
|
|
v0.35.2
patch
|
v0.35.2
patch
Dependencies (4)
|
|
v0.35.1
patch
|
v0.35.1
patch
Dependencies (4)
|
|
v0.35.0
minor
|
v0.35.0
minor
Dependencies (4)
|
|
v0.34.0
minor
|
v0.34.0
minor
Dependencies (4)
|
|
v0.33.0
minor
|
v0.33.0
minor
Dependencies (4)
|
|
v0.32.0
minor
|
v0.32.0
minor
Dependencies (4)
|
|
v0.31.2
patch
|
v0.31.2
patch
Dependencies (4)
|
|
v0.31.0
minor
|
v0.31.0
minor
Dependencies (4)
|
|
v0.30.0
minor
|
v0.30.0
minor
Dependencies (4)
|
|
v0.29.1
patch
|
v0.29.1
patch
Dependencies (4)
|
|
v0.29.0
minor
|
v0.29.0
minor
Dependencies (4)
|
|
v0.28.0
minor
|
v0.28.0
minor
Dependencies (4)
|
|
v0.27.1
patch
|
v0.27.1
patch
Dependencies (4)
|
|
v0.27.0
minor
|
v0.27.0
minor
Dependencies (4)
|
|
v0.25.0
minor
|
v0.25.0
minor
Dependencies (4)
|
|
v0.23.1
minor
|
v0.23.1
minor
Dependencies (4)
|
|
v0.22.1
patch
|
v0.22.1
patch
Dependencies (4)
|
|
v0.22.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.22.0
minor
Dependencies (4)
|
|
v0.21.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.21.0
minor
Dependencies (4)
|
|
v0.19.4
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.19.4
patch
Dependencies (4)
|
|
v0.19.2
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.19.2
patch
Dependencies (4)
|
|
v0.19.1
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.19.1
patch
Dependencies (4)
|
|
v0.19.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.19.0
minor
Dependencies (4)
|
|
v0.18.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.18.0
minor
Dependencies (4)
|
|
v0.17.2
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.17.2
patch
Dependencies (4)
|
|
v0.17.1
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.17.1
patch
Dependencies (4)
|
|
v0.17.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.17.0
minor
Dependencies (4)
|
|
v0.16.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.16.0
minor
Dependencies (4)
|
|
v0.14.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.14.0
minor
Dependencies (3)
|
|
v0.13.2
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.13.2
patch
Dependencies (3)
|
|
v0.13.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.13.0
minor
Dependencies (3)
|
|
v0.12.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.12.0
minor
Dependencies (3)
|
|
v0.11.1
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.11.1
patch
Dependencies (3)
|
|
v0.11.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.11.0
minor
Dependencies (3)
|
|
v0.9.1
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.22.1
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.9.1
patch
Dependencies (3)
|