← Home

minitask

npm Repository Homepage

A standard/convention for running tasks over a list of files based around Node core streams2

9
Versions
BSD
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

mixu

Keywords

tasktasksbuildjobrunmake

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 13+ years old with 9 versions and a reputable publisher (mixu, 86 approved packages). The 0.0.0 version is a legitimate early versioning choice, not a malicious indicator. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in cache.js loads a local JSON metadata file from a user-provided path — standard Node.js JSON loading pattern, not arbitrary code execution. ai
license uncommon-license:BSD AI (license): BSD is a well-known permissive open source license; the uncommon-license flag is a false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
0.2.3 2 / 2
0.2.2 2 / 2
0.2.1 2 / 2
0.2.0 2 / 2
0.1.2 1 / 2
0.1.1 1 / 2
0.1.0 1 / 2
0.0.1 0 / 1
0.0.0 0 / 0

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

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

1 finding
LOW No provenance attestation provenance

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

v0.0.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.