DingTalk
How to install
The Jenkins project announced an unresolved security vulnerability affecting the current version of this plugin (
why?
):
SSL/TLS certificate validation unconditionally disabled
Documentation
Releases
Issues
Dependencies
Health Score
65
%
health score
Adoption
60%
There are 471 days between last release and last commit.
Less than 2 years between last release and last commit.
20%
The plugin is not marked as up for adoption.
100%
Deprecation
100%
The repository is not archived.
100%
Plugin is not marked as deprecated.
100%
The plugin appears in the update-center.
100%
Documentation
100%
Documentation is in plugin repository.
100%
Plugin is not using Release Drafter to manage its changelog.
Plugin could benefit from using Release Drafter.
0%
Plugin seems to have a dedicated contributing guide.
100%
Plugin seems to have a correct description.
100%
Repository Configuration
100%
Code Ownership definition found and is valid.
100%
Dependabot is configured.
0 open dependency pull request
100%
Jenkinsfile detected in plugin repository.
100%
JEP-229 is not configured on the plugin.
This is not mandatory, but can help reduce time between pull requests merge and feature / bugfix availability.
See how to setup JEP-229 on the plugin.
0%
Security
0%
Plugin seem to have on-going security advisory.
SECURITY-3353
0%
Computed:
2 days ago
Version: 2.7.3
Released:
about a year ago
Requires Jenkins 2.426
ID: dingding-notifications
Installed on 2.50% of controllers
View detailed version information
Links
GitHub
Open issues (Github)
Report an issue (Github)
Open issues (Jira)
Report an issue (Jira)
Pipeline Step Reference
Javadoc
Labels
Build Notifiers
Maintainers
liu wei
Bob
Help us improve this page!
To propose a change submit a pull request to
the plugin page
on GitHub.
Previous Security Warnings
Credentials stored in plain text
Affects version 1.9 and earlier