@atom8n/di
`@n8n/di` is a dependency injection (DI) container library, based on [`typedi`](https://github.com/typestack/typedi).
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @atom8n/di is a DI library, not a typosquat of pg; edit-distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @atom8n/di is a DI library, not a typosquat of qs; edit-distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @atom8n/di is a DI library, not a typosquat of joi; edit-distance match is coincidental. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.13.7 | 1 / 1 | |
| 0.13.6 | 1 / 1 | |
| 0.13.5 | 1 / 1 | |
| 0.13.4 | 1 / 1 | |
| 0.13.3 | 1 / 1 | |
| 0.13.2 | 1 / 1 | |
| 0.13.1 | 1 / 1 | |
| 0.13.0 | 1 / 1 | |
| 0.12.3 | 1 / 1 | |
| 0.12.2 | 1 / 1 | |
| 0.12.1 | 1 / 1 | |
| 0.12.0 | 1 / 1 | |
| 0.11.0 | 1 / 1 | |
| 0.10.9 | 1 / 1 | |
| 0.10.8 | 1 / 1 | |
| 0.10.7 | 1 / 1 | |
| 0.10.6 | 1 / 1 | |
| 0.10.5 | 1 / 1 | |
| 0.10.4 | 1 / 1 | |
| 0.10.3 | 1 / 1 | |
| 0.10.2 | 1 / 1 | |
| 0.10.1 | 1 / 1 | |
| 0.10.0 | 1 / 1 |
v0.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.