@inversifyjs/core
InversifyJs core package
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @inversifyjs/core is the official InversifyJS core; 'core' coincidentally matches 'cors' by edit distance but is unrelated. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; short README and semver start at 1.1.0 are normal for InversifyJS monorepo restructuring. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 3 / 13 | |
| 10.0.0 | 3 / 13 | |
| 9.2.0 | 3 / 14 | |
| 9.1.2 | 3 / 14 | |
| 9.1.1 | 3 / 14 | |
| 9.1.0 | 3 / 14 | |
| 9.0.1 | 3 / 14 | |
| 9.0.0 | 3 / 14 | |
| 8.0.0 | 3 / 14 | |
| 7.2.0 | 3 / 14 | |
| 7.1.1 | 3 / 14 | |
| 7.1.0 | 3 / 14 | |
| 7.0.1 | 3 / 14 | |
| 7.0.0 | 3 / 14 | |
| 6.0.1 | 3 / 14 | |
| 6.0.0 | 3 / 14 | |
| 5.4.0 | 3 / 14 | |
| 5.3.3 | 3 / 14 | |
| 5.3.2 | 3 / 14 | |
| 5.3.1 | 3 / 14 | |
| 5.3.0 | 3 / 14 | |
| 5.2.0 | 3 / 14 | |
| 5.1.0 | 3 / 14 | |
| 5.0.0 | 3 / 14 | |
| 4.0.1 | 3 / 15 | |
| 4.0.0 | 3 / 15 | |
| 3.5.0 | 3 / 15 | |
| 3.4.0 | 3 / 15 | |
| 3.3.0 | 3 / 15 | |
| 3.2.0 | 3 / 19 | |
| 3.1.0 | 3 / 19 | |
| 3.0.2 | 3 / 19 | |
| 3.0.1 | 3 / 19 | |
| 3.0.0 | 3 / 19 | |
| 2.2.0 | 3 / 19 | |
| 2.1.0 | 3 / 19 | |
| 2.0.0 | 3 / 19 | |
| 1.3.5 | 2 / 19 | |
| 1.3.4 | 2 / 18 | |
| 1.3.3 | 2 / 15 | |
| 1.3.2 | 2 / 15 | |
| 1.3.1 | 2 / 15 | |
| 1.3.0 | 2 / 15 | |
| 1.2.0 | 2 / 15 | |
| 1.1.2 | 2 / 15 | |
| 1.1.1 | 2 / 15 | |
| 1.1.0 | 2 / 14 | |
| 10.0.0-beta.0 | 3 / 13 |
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsPackage name '@inversifyjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.