← Home

promised-io

npm Repository Homepage

Promise-based IO

8
Versions
—
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

Kris Zypkriszyp

Keywords

promiseio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Located in a Rhino JS engine compatibility shim; new Function() is used only when callback is a string, a deliberate legacy design choice, not a security risk in this context. ai
semgrep semgrep:dynamic-require AI (semgrep): Flagged line is standard UMD/AMD boilerplate for module compatibility; deps are statically declared, not user-controlled arbitrary input. ai
publish-pattern dormant-publish AI (publish-pattern): kriszyp is a well-established publisher with 1024 approved packages; dormancy is consistent with a mature, stable utility package rather than account takeover. ai

Versions (showing 8 of 8)

Version Deps Published
0.3.6 0 / 2
0.3.5 0 / 2
0.3.4 0 / 2
0.3.3 0 / 2
0.3.0 0 / 2
0.2.3 0 / 0
0.2.2 1 / 0
0.0.1 0 / 0

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

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