hubot-slack
Advanced tools
Comparing version 4.0.0 to 4.0.1
# [slack-hubot] Changelog | ||
### v4.0.0 (2016-06-15) | ||
### v4.0.1 (2016-07-19) | ||
* Usernames with `-` and `.` no longer borked | ||
* You could craft a bot that would crash Hubot by simply having it send a message. Wow! That got fixed. | ||
### v4.0.0 (2016-07-15) | ||
* Now uses the latest version of `node-slack-sdk` (v3.4.1 as of this writing), inheriting all the improvements therein. | ||
@@ -15,2 +19,2 @@ * Better (and automatically enabled) reconnect logic. As in, it actually reconnects automatically at all. | ||
* Total refactoring of the functionality, exposing a slightly different interface. So watch out for that. | ||
* You can now access the underlying Slack client directly, for when you really need low-level functionality therein. | ||
* You can now access the underlying Slack client directly, for when you really need low-level functionality therein. |
{ | ||
"name": "hubot-slack", | ||
"version": "4.0.0", | ||
"version": "4.0.1", | ||
"description": "A Slack adapter for hubot", | ||
@@ -5,0 +5,0 @@ "main": "./slack", |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
213872
37
1141
1
2