← Home

matchdep

npm Repository Homepage

Use micromatch to filter npm module dependencies by name.

8
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

phatedtkellen

Keywords

package.jsondependenciesdevDependenciespeerDependencies

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer from tkellen to phated (both Gulp/Grunt ecosystem maintainers); phated is a highly trusted publisher. ai
maintainer-change maintainer-added AI (maintainer-change): phated added as maintainer in 2015; well-known ecosystem contributor with extensive track record. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require of a config path is the core documented functionality of matchdep; not a security concern. ai
provenance no-provenance AI (provenance): Published in 2015, before Sigstore provenance existed. Stable for this package. ai

Versions (showing 8 of 8)

Version Deps Published
2.0.0 4 / 3
1.0.1 4 / 3
1.0.0 4 / 3
0.3.0 4 / 3
0.2.0 1 / 4
0.1.2 1 / 4
0.1.1 1 / 4
0.1.0 1 / 4

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.

v1.0.1

2 findings
HIGH Publisher changed: tkellen → phated (on 2016-02-09) provenance

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

2 findings
HIGH Publisher changed: tkellen → phated (on 2015-09-27) provenance

This version was published by a different npm account than previous versions on 2015-09-27. 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.