← Home

loop

npm Repository Homepage

loop through commands in fun and amazing ways!

20
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

mateodelnortepatrickleet

Keywords

loopcommandcommands

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change to mateodelnorte is legitimate: repo URL matches their GitHub org, they have 110 approved packages and 0 rejected, and the transfer occurred in 2017 with no subsequent issues. ai
maintainer-change maintainer-added AI (maintainer-change): mateodelnorte is the new canonical maintainer with a strong track record; the GitHub repo URL confirms the transfer is legitimate. ai
phantom-deps phantom-dep:mocha AI (phantom-deps): mocha is a test framework declared in dependencies instead of devDependencies; packaging hygiene issue, not a security concern. ai
phantom-deps phantom-dep:yargs AI (phantom-deps): yargs is a well-known CLI arg parser; phantom dep finding reflects it being used indirectly, not a security concern. ai
phantom-deps phantom-dep:should AI (phantom-deps): should is a test assertion library declared in dependencies instead of devDependencies; packaging hygiene issue, not a security concern. ai

Versions (showing 20 of 20)

Version Deps Published
3.3.6 7 / 11
3.3.5 7 / 13
3.3.4 7 / 13
3.3.3 7 / 13
3.3.2 7 / 10
3.3.1 7 / 10
3.3.0 7 / 10
3.2.0 7 / 10
3.1.4 7 / 10
3.1.3 8 / 1
3.1.2 8 / 1
3.1.1 8 / 1
3.0.6 8 / 0
3.0.3 8 / 0
3.0.2 8 / 0
3.0.1 8 / 0
3.0.0 8 / 0
2.1.2 1 / 0
2.1.1 1 / 0
1.0.0 8 / 1

v3.3.6

1 finding
LOW No provenance attestation provenance

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

v3.3.5

1 finding
LOW No provenance attestation provenance

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

v3.3.4

1 finding
LOW No provenance attestation provenance

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

v3.3.3

1 finding
LOW No provenance attestation provenance

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

v3.3.2

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

2 findings
HIGH Publisher changed: coolaj86 → mateodelnorte (on 2017-04-22) provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.