← Home

inversify

npm Repository Homepage

A powerful and lightweight inversion of control container for JavaScript and Node.js apps powered by TypeScript.

88
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

remojansenjameskmongerdcavanaghnotaphplover

Keywords

dependency injectiondependency inversiondiinversion of control containeriocjavascriptnodetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:lib/esm/index.js AI (source-diff): lib/esm/index.js is a rollup+terser minified ESM bundle, as confirmed by the build:esm script using @rollup/plugin-terser. Content is readable minified InversifyJS source, not obfuscation. ai
source-diff large-new-source-files AI (source-diff): New files result from build system refactoring (AMD/ES/lib outputs replaced with CJS+ESM dual-package structure). Legitimate restructuring, not injected code. ai
source-diff source-size-dropped AI (source-diff): Size drop from 1MB to 254KB reflects removal of legacy AMD/ES/lib build outputs in favor of a leaner CJS+ESM dual-package structure. ai
provenance missing-githead AI (provenance): inversify is a well-established package; missing gitHead reflects a publish environment change, not a security concern. No other suspicious signals present. ai
provenance no-provenance AI (provenance): InversifyJS is a well-established package with a trusted publisher; lack of Sigstore provenance is a process gap, not a security threat for this package. ai

Versions (showing 88 of 88)

Hide prereleases
Version Deps Published
8.1.0 3 / 10
8.0.0 3 / 10
7.11.0 3 / 11
7.10.8 3 / 11
7.10.7 3 / 11
7.10.6 3 / 11
7.10.5 3 / 11
7.10.4 3 / 11
7.10.3 3 / 11
7.10.2 3 / 11
7.10.1 3 / 11
7.10.0 3 / 26
7.9.1 3 / 26
7.9.0 3 / 26
7.8.1 3 / 26
7.8.0 3 / 26
7.7.1 3 / 26
7.7.0 3 / 26
7.6.1 3 / 23
7.6.0 3 / 23
7.5.4 3 / 23
7.5.3 3 / 23
7.5.2 3 / 23
7.5.1 3 / 23
7.5.0 3 / 23
7.4.0 3 / 23
7.3.0 3 / 23
7.2.0 3 / 23
7.1.0 3 / 23
7.0.2 3 / 23
7.0.1 3 / 23
7.0.0 3 / 23
6.2.2 2 / 23
6.2.1 2 / 23
6.2.0 2 / 23
6.1.6 2 / 23
6.1.5 2 / 23
6.1.4 2 / 25
6.1.3 2 / 22
6.1.2 2 / 22
6.1.1 2 / 22
6.0.2 0 / 14
6.0.1 0 / 27
5.1.1 0 / 31
5.1.0 0 / 31
5.0.5 0 / 44
5.0.1 0 / 41
4.14.0 0 / 41
4.13.0 0 / 41
4.11.1 0 / 41
4.11.0 0 / 41
4.10.0 0 / 41
4.9.0 0 / 41
4.8.0 0 / 41
4.7.0 0 / 41
4.6.1 0 / 41
4.6.0 0 / 41
4.5.2 0 / 41
4.5.1 0 / 41
4.5.0 0 / 41
4.4.0 0 / 41
4.3.0 0 / 41
4.2.0 0 / 41
4.1.1 0 / 41
4.1.0 0 / 41
4.0.0 0 / 41
3.3.0 0 / 41
3.2.0 0 / 41
3.1.0 0 / 40
3.0.0 0 / 40
2.0.1 0 / 40
2.0.0 0 / 40
1.3.1 0 / 19
1.3.0 0 / 19
1.2.2 0 / 19
1.2.1 0 / 18
1.2.0 0 / 22
1.0.3 0 / 22
1.0.2 0 / 22
1.0.1 0 / 23
1.0.0 0 / 22
0.0.7 0 / 21
0.0.6 0 / 20
0.0.5 0 / 20
0.0.4 0 / 20
0.0.2 0 / 20
0.0.1 0 / 20
8.0.0-beta.0 3 / 10

v8.1.0

1 finding
LOW No provenance attestation provenance

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

v8.0.0

1 finding
LOW No provenance attestation provenance

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

v7.11.0

1 finding
LOW No provenance attestation provenance

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

v7.10.8

1 finding
LOW No provenance attestation provenance

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

v7.10.7

1 finding
LOW No provenance attestation provenance

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

v7.10.6

1 finding
LOW No provenance attestation provenance

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

v7.10.5

1 finding
LOW No provenance attestation provenance

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

v7.10.4

1 finding
LOW No provenance attestation provenance

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

v7.10.3

1 finding
INFO No provenance attestation provenance

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

v7.10.2

1 finding
INFO No provenance attestation provenance

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

v7.10.1

1 finding
INFO No provenance attestation provenance

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

v7.10.0

1 finding
INFO No provenance attestation provenance

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

v7.9.1

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: notaphplover.

v7.9.0

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: notaphplover.

v7.8.1

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: notaphplover.

v7.8.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: notaphplover.

INFO No provenance attestation provenance

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

v7.7.1

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: notaphplover.

v7.7.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: notaphplover.

LOW No provenance attestation provenance

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

v7.6.1

1 finding
LOW No provenance attestation provenance

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

v7.6.0

1 finding
LOW No provenance attestation provenance

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

v7.5.4

1 finding
INFO No provenance attestation provenance

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

v7.5.3

1 finding
INFO No provenance attestation provenance

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

v7.5.2

1 finding
LOW No provenance attestation provenance

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

v7.5.1

1 finding
INFO No provenance attestation provenance

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

v7.5.0

1 finding
INFO No provenance attestation provenance

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

v7.4.0

1 finding
INFO No provenance attestation provenance

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

v7.3.0

1 finding
INFO No provenance attestation provenance

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

v7.2.0

1 finding
INFO No provenance attestation provenance

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

v7.1.0

1 finding
INFO No provenance attestation provenance

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

v7.0.2

1 finding
INFO No provenance attestation provenance

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

v7.0.1

1 finding
INFO No provenance attestation provenance

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

v7.0.0

1 finding
INFO No provenance attestation provenance

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

v6.2.2

1 finding
INFO No provenance attestation provenance

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

v6.2.1

1 finding
INFO No provenance attestation provenance

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

v6.2.0

1 finding
INFO No provenance attestation provenance

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

v6.1.6

1 finding
INFO No provenance attestation provenance

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

v6.1.5

2 findings
HIGH New obfuscated file: lib/esm/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v6.1.4

1 finding
LOW No provenance attestation provenance

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

v6.1.3

1 finding
INFO No provenance attestation provenance

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

v6.1.2

1 finding
INFO No provenance attestation provenance

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

v6.1.1

1 finding
INFO No provenance attestation provenance

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