
Security News
November CVEs Fell 25% YoY, Driven by Slowdowns at Major CNAs
November CVE publications fell 25% YoY even as 2025 totals rose, showing how a few major CNAs can swing “global” counts and skew perceived risk.
@atomist/slack-messages
Advanced tools
Atomist utilities for creating formatted Slack messages
Node.js module that helps to create well-formatted
Slack messages sent through the @atomist bot from your
software delivery machine (SDM). This module also facilitates adding
actions to your Slack messages that execute SDM commands.
Support for sending Slack Block messages is also supported.
See the Atomist documentation for more information on what SDMs are and what they can do for you using the Atomist API for software.
Construct a message as a plain map following the Slack message formatting API.
import { SlackMessage } from "@atomist/slack-messages";
// A very simple message
const msg: SlackMessage = { text: "Simple message" };
import {
escape,
SlackMessage,
url,
} from "@atomist/slack-messages";
// Here is an example of a message with a Slack action (button).
const msg: SlackMessage = {
text: `${url(user.url, "@" + user.name)} opened issue: ${url(issue.url, issue.title)}`,
attachments: [
{
text: escape(issue.body),
fallback: escape(issue.title),
mrkdwn_in: ["text"],
actions: [
{
text: "Close issue",
type: "button",
name: "closeissue",
value: "somebuttonid",
},
],
callback_id: "cllbck1",
},
],
};
And then render the message with render(msg). This will construct a
JSON string representation of the message:
import { render } from "@atomist/slack-messages"
const renderedMsg = render(msg);
or to produce a pretty JSON string:
const renderedMsg = render(msg, true);
This will produce the following JSON string (pretty version):
{
"text": "<https://github.com/anna|@anna> opened issue: <https://github.com/someorg/somerepo/issues/484|This issue title contains <unsafe> characters and &>",
"attachments": [
{
"text": "This is a very important issue with body containing <unsafe> characters and even &",
"fallback": "This issue title contains <unsafe> characters and &",
"mrkdwn_in": [
"text"
],
"callback_id": "cllbck1",
"actions": [
{
"text": "Close issue",
"type": "button",
"name": "rug",
"value": "somebuttonid"
}
]
}
]
}
Note that the render function will automatically assign a unique
callback_id to each attachments that has actions. But, if you
provide your custom callback_id it will be preserved as is.
escape("Slack requires you to escape <, > and &");
// => "Slack requires you to escape <, > and &"
// Simple link
url("https://www.atomist.com");
// => "<https://www.atomist.com>"
// Link with label
url("https://www.atomist.com", "atomist");
// => "<https://www.atomist.com|atomist>"
// @some-user (Slack will display user name for provided user ID)
user("U123");
// => "<@U123>"
// #some-channel (Slack will display channel name for provided channel ID)
channel("C123");
// => "<#C123>"
// @channel
atChannel();
// => "<!channel>"
// @here
atHere();
// => "<!here>"
// @everyone
atEveryone();
// => "<!everyone>"
emoji("smile");
// => ":smile:";
Slack will render markdown if field where markdown is present is
included in mrkdwn_in array.
bold("This text will appear bold");
// => "*This text will appear bold*"
italic("This text will appear italic");
// => "_This text will appear italic_"
strikethrough("This text will appear strike-through");
// => "~This text will appear strike-through~"
// Single line code block
codeLine("var a = new A();");
// => "`var a = new A();`"
// Multi line code block
codeBlock("var a = new A();\nvar b = new B();");
// => "```var a = new A();\nvar b = new B();```"
// List
listItem("Item 1");
// => "• Item 1"
GitHub and Slack markdown are different enough to make your GitHub
issues or GitHub PRs look quite bad in Slack by default. You can use
the githubToSlack function from Markdown to convert text that uses
GitHub markdown to text that will look good in Slack:
import { githubToSlack } from "@atomist/slack-messages"
githubToSlack("* list item 1\n* list item 2\n\**some bold text** and *some italic text* with a link [click here](http://someplace.com)");
// => "• list item 1\n• list item 2\n*some bold text* and _some italic text_ with a link <http://someplace.com|click here>"
General support questions should be discussed in the #help
channel in the Atomist community Slack workspace.
If you find a problem, please create an issue.
You will need to install Node.js to build and test this project.
Install dependencies.
$ npm install
Use the build package script to compile, test, lint, and build the
documentation.
$ npm run build
Releases are handled via the Atomist SDM. Just press the 'Approve' button in the Atomist dashboard or Slack.
Created by Atomist. Need Help? Join our Slack workspace.
FAQs
Atomist utilities for creating formatted Slack messages
The npm package @atomist/slack-messages receives a total of 12,892 weekly downloads. As such, @atomist/slack-messages popularity was classified as popular.
We found that @atomist/slack-messages demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
November CVE publications fell 25% YoY even as 2025 totals rose, showing how a few major CNAs can swing “global” counts and skew perceived risk.

Security News
React disclosed a CVSS 10.0 RCE in React Server Components and is advising users to upgrade affected packages and frameworks to patched versions now.

Research
/Security News
We spotted a wave of auto-generated “elf-*” npm packages published every two minutes from new accounts, with simple malware variants and early takedowns underway.