grunt-sync MIT 25 versions

grunt-sync

npm Repository Homepage

Task to synchronize two directories. Similar to grunt-copy but updates only files that have been changed.

25

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

tomusdrw

Keywords

gruntpluginsyncsynchronizecopy

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:grunt-complexity	AI (npm-metadata): URL dep points to the same author's own GitHub repo (tomusdrw/grunt-complexity); consistent with author using their own fork. Not a supply-chain risk for this package.	ai	2026/04/24
phantom-deps	phantom-dep:grunt	AI (phantom-deps): Grunt plugins conventionally declare grunt as a dependency; it's referenced in Gruntfile.js for build tooling, not a runtime import issue.	ai	2026/04/24
phantom-deps	phantom-dep:grunt-complexity	AI (phantom-deps): Build/lint tooling referenced in Gruntfile.js only; not a runtime security concern for this package.	ai	2026/04/24
phantom-deps	phantom-dep:grunt-simple-mocha	AI (phantom-deps): Test tooling referenced in Gruntfile.js only; not a runtime security concern for this package.	ai	2026/04/24
phantom-deps	phantom-dep:grunt-contrib-jshint	AI (phantom-deps): Lint tooling referenced in Gruntfile.js only; not a runtime security concern for this package.	ai	2026/04/24

Versions (showing 25 of 25)

Version	Deps	Published
0.8.2	3 / 9	2020-01-14
0.8.1	3 / 9	2019-05-20
0.8.0	3 / 9	2018-06-22
0.7.0	4 / 9	2017-09-24
0.6.2	4 / 8	2016-08-09
0.5.2	4 / 8	2016-02-02
0.5.1	4 / 8	2015-12-11
0.5.0	4 / 8	2015-12-10
0.4.1	4 / 8	2015-08-31
0.4.0	4 / 8	2015-08-31
0.3.0	4 / 8	2015-08-21
0.2.4	3 / 8	2015-07-26
0.2.3	3 / 7	2015-01-11
0.2.2	2 / 7	2014-11-23
0.2.1	2 / 7	2014-11-08
0.2.0	2 / 7	2014-09-04
0.1.1	2 / 7	2014-08-26
0.1.0	2 / 7	2014-08-25
0.0.8	1 / 6	2014-07-31
0.0.7	1 / 6	2014-04-21
0.0.6	1 / 6	2014-03-25
0.0.5	1 / 6	2013-12-16
0.0.4	1 / 6	2013-04-02
0.0.3	1 / 6	2013-02-23
0.0.2	5 / 2	2013-02-23

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

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.2

1 finding

LOW No provenance attestation provenance

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

v0.5.2

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.1

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.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.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

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.1

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

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.