Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Further maintenance of Viper #798

Open
ITSEC-DACHSER opened this issue Apr 4, 2022 · 1 comment
Open

Further maintenance of Viper #798

ITSEC-DACHSER opened this issue Apr 4, 2022 · 1 comment

Comments

@ITSEC-DACHSER
Copy link

Dear maintainer,

first, we would like to thank you for the development of Viper in the last years. In our opinion, Viper is a very handy, valuable and nice tool, which is a fixed part in our eco-system and therefore is used everyday via the (old) API.

Since the last release is been a while, we would like to ask, if there is any chance that Viper, the API and the modules will be further developed in future?

Best regards

@botherder
Copy link
Member

I would be happy to see the tool be developed forward. The time I have to dedicate to this is limited. I would be happy to act in a reviewer function, merge PRs, fix bugs, etc. Unfortunately I am not sure there are others interested in continuing core development at this point.
It is also not fully clear what is the active user base at this point.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants