grunt-contrib-concat MIT 13 versions

grunt-contrib-concat

npm Repository Homepage

Concatenate files.

13

Versions

MIT

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

cowboyjmeastkellenvladikoffshamasindresorhus

Keywords

gruntplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from shama to vladikoff reflects a documented Grunt team maintainer transition in 2021; vladikoff is a long-standing trusted publisher within the gruntjs org. Stable for this package.	ai	2026/04/24

Versions (showing 13 of 13)

Version	Deps	Published
2.1.0	2 / 5	2022-04-03
2.0.0	2 / 5	2021-10-08
1.0.1	2 / 5	2016-04-20
1.0.0	2 / 6	2016-02-21
0.5.1	2 / 6	2015-02-20
0.5.0	2 / 5	2014-07-20
0.4.0	1 / 5	2014-03-31
0.3.0	0 / 5	2013-04-26
0.2.0	0 / 5	2013-04-08
0.1.3	0 / 5	2013-02-22
0.1.2	0 / 5	2013-02-18
0.1.1	0 / 6	2012-12-04
0.1.0	0 / 5	2012-10-05

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Publisher changed: shama → vladikoff (on 2021-10-08) provenance

This version was published by a different npm account than previous versions on 2021-10-08. 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.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

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sindresorhus → shama (on 2016-02-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-02-21. This could indicate a legitimate maintainer transition or an account compromise.

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.