← Home

@dreamkit/ioc

npm Repository Homepage

A simple and lightweight IoC container for TypeScript.

14
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

juanrgm

Keywords

iocdependency injectiondependencyinjectioncontainertypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped @dreamkit/ioc is an IoC container, not a typosquat of koa; coincidental Levenshtein match. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped @dreamkit/ioc is an IoC container, not a typosquat of got; coincidental Levenshtein match. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @dreamkit/ioc is an IoC container, not a typosquat of joi; coincidental Levenshtein match. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @dreamkit/ioc is an IoC container, not a typosquat of zod; coincidental Levenshtein match. ai

Versions (showing 14 of 14)

Version Deps Published
0.5.3 1 / 1
0.5.2 1 / 1
0.5.1 1 / 1
0.5.0 1 / 1
0.4.1 1 / 1
0.4.0 1 / 1
0.3.4 1 / 1
0.3.3 1 / 1
0.3.2 1 / 1
0.3.1 1 / 1
0.3.0 1 / 1
0.2.1 1 / 1
0.2.0 1 / 1
0.1.0 1 / 1

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

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

v0.4.0

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

1 finding
LOW No provenance attestation provenance

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

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

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

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

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