← Home

@noego/ioc

npm
17
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

shavyg2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped IoC container package; edit-distance match to koa is coincidental, not impersonation. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped IoC container package; edit-distance match to got is coincidental, not impersonation. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped IoC container package; edit-distance match to joi is coincidental, not impersonation. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped IoC container package; edit-distance match to zod is coincidental, not impersonation. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types packages are type-only and loaded by convention, not direct import. ai
phantom-deps phantom-dep:@types/randomstring AI (phantom-deps): @types packages are type-only and loaded by convention, not direct import. ai
phantom-deps phantom-dep:@types/reflect-metadata AI (phantom-deps): @types packages are type-only and loaded by convention, not direct import. ai

Versions (showing 17 of 17)

Version Deps Published
0.3.1 5 / 6
0.3.0 5 / 6
0.2.3 5 / 6
0.2.2 5 / 6
0.2.1 7 / 8
0.2.0 7 / 8
0.1.0 7 / 8
0.0.11 7 / 8
0.0.10 7 / 8
0.0.9 5 / 6
0.0.8 5 / 6
0.0.7 5 / 5
0.0.6 5 / 5
0.0.5 5 / 5
0.0.4 5 / 5
0.0.3 5 / 5
0.0.2 5 / 5

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

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

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

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.

v0.0.11

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

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

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

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

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

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

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

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

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

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.