← Home

chainit

npm Repository Homepage

Turn an asynchronous JavaScript api into an asynchronous chainable JavaScript api.

14
Versions
MIT/X11
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

vvochristian-bromann

Keywords

chainasyncqueueflow controlchainablechainifychainitchain api

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from vvo to christian-bromann occurred in 2014; christian-bromann is a well-established publisher. This is a historical, legitimate maintainer transition, not a suspicious takeover. ai
maintainer-change maintainer-added AI (maintainer-change): Same as publisher-changed: this is a decade-old legitimate maintainer transition to a well-known npm publisher. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() is the core mechanism of chainit — it wraps constructor methods to build a chainable API. This is intentional and documented behavior for this library, not a security risk. ai

Versions (showing 14 of 14)

Version Deps Published
2.1.1 1 / 2
2.1.0 1 / 2
2.0.4 1 / 2
2.0.3 1 / 2
1.3.1 1 / 2
1.3.0 1 / 2
1.2.0 1 / 2
1.1.2 1 / 2
1.1.1 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2
0.0.4 1 / 2
0.0.3 1 / 1
0.0.1 1 / 1

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

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

2 findings
HIGH Publisher changed: vvo → christian-bromann (on 2014-04-18) provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

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

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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