@atomist/slack-messages Apache-2.0 22 versions

@atomist/slack-messages

npm Repository Homepage

Atomist utilities for creating formatted Slack messages

22

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

atomist-botddatomistcdupuisslimslenderslacks

Keywords

atomistautomationsdmslack

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Transition from 'atomist' account to named Atomist org members (atomist-bot, cdupuis, ddatomist, slimslenderslacks) is an internal org restructuring, not a hostile takeover. All new maintainers are known Atomist team members.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): Publisher change from 'atomist' to 'atomist-bot' reflects Atomist org account restructuring. atomist-bot has a clean track record (21 approved, 0 rejected) and is the org's automation account.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are all known Atomist organization members; addition is part of legitimate org account restructuring.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of generic 'atomist' account in favor of named individual accounts is a legitimate org restructuring, not a compromise indicator.	ai	2026/04/23

Versions (showing 22 of 22)

Version	Deps	Published
1.2.2	0 / 17	2021-03-15
1.2.1	0 / 17	2020-11-24
1.2.0	0 / 17	2020-10-07
1.1.1	0 / 12	2019-06-18
1.1.0	0 / 12	2018-11-15
1.0.1	0 / 10	2018-11-09
1.0.0	0 / 10	2018-08-30
0.12.1	2 / 11	2017-11-09
0.12.0	2 / 11	2017-09-20
0.11.0	3 / 9	2017-08-18
0.10.0	3 / 8	2017-08-18
0.9.0	3 / 8	2017-08-17
0.8.0	3 / 8	2017-08-14
0.7.0	1 / 9	2017-07-04
0.6.0	1 / 9	2017-05-16
0.5.1	1 / 9	2017-05-15
0.5.0	1 / 9	2017-05-15
0.4.0	1 / 9	2017-05-10
0.3.1	1 / 9	2017-05-10
0.3.0	1 / 9	2017-05-10
0.2.0	1 / 9	2017-05-09
0.1.0	1 / 9	2017-05-09

v1.2.2

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (atomist) were replaced by new maintainers (atomist-bot, ddatomist, cdupuis, slimslenderslacks). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: atomist → atomist-bot (on 2021-03-15) provenance

This version was published by a different npm account than previous versions on 2021-03-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.