← Home

gulp-sourcemaps

npm Repository Homepage

Sourcemap support for gulpjs.

51
Versions
ISC
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

phatedfloridoonmccready

Keywords

gulpplugingulpsource mapssourcemaps

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from phated to nmccready (both known Gulp ecosystem contributors) in 2018; stable for this package. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; no CI/CD attestation expected for this era of publishing. ai

Versions (showing 51 of 66)

View all versions
Version Deps Published
3.0.0 11 / 17
2.6.5 11 / 18
2.6.4 11 / 18
2.6.3 11 / 18
2.6.2 11 / 18
2.6.1 12 / 17
2.6.0 12 / 17
2.5.2 11 / 17
2.5.1 11 / 17
2.5.0 11 / 17
2.4.1 10 / 16
2.4.0 10 / 16
2.3.1 10 / 15
2.3.0 10 / 14
2.2.3 10 / 14
2.2.2 10 / 12
2.2.0 10 / 6
2.1.1 10 / 6
2.0.1 10 / 6
2.0.0 9 / 5
1.12.1 11 / 17
1.12.0 11 / 17
1.11.1 10 / 16
1.11.0 10 / 16
1.10.1 10 / 15
1.10.0 10 / 14
1.9.3 10 / 14
1.9.2 10 / 12
1.9.1 10 / 8
1.9.0 10 / 6
1.8.1 10 / 6
1.7.3 10 / 6
1.7.1 9 / 5
1.6.0 5 / 5
1.5.2 5 / 5
1.5.1 5 / 5
1.5.0 5 / 5
1.4.0 3 / 5
1.3.0 3 / 6
1.2.8 3 / 6
1.2.7 3 / 6
1.2.6 3 / 6
1.2.5 3 / 6
1.2.4 3 / 6
1.2.3 3 / 6
1.2.2 3 / 6
1.2.1 3 / 6
1.2.0 3 / 6
1.1.5 3 / 6
1.1.4 3 / 6
1.1.3 3 / 6

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.6.5

1 finding
INFO No provenance attestation provenance

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

v2.6.4

2 findings
HIGH Publisher changed: phated → nmccready (on 2018-01-22) provenance

This version was published by a different npm account than previous versions on 2018-01-22. 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.

v2.6.3

2 findings
HIGH Publisher changed: phated → nmccready (on 2018-01-02) provenance

This version was published by a different npm account than previous versions on 2018-01-02. 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.

v2.6.2

1 finding
LOW No provenance attestation provenance

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

v2.6.1

2 findings
HIGH Publisher changed: phated → nmccready (on 2017-08-18) provenance

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

v2.6.0

1 finding
INFO No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
INFO No provenance attestation provenance

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

v2.4.1

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
INFO No provenance attestation provenance

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

v2.2.3

1 finding
INFO No provenance attestation provenance

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

v2.2.2

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.0.1

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

1 finding
LOW No provenance attestation provenance

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