← Home

@nextrush/di

npm Repository Homepage

Lightweight dependency injection container for NextRush

5
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

0xtanzim

Keywords

nextrushdidependency-injectionioccontainertypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @nextrush/di; not a typosquat of pg. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @nextrush/di; not a typosquat of qs. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @nextrush/di; not a typosquat of joi. ai

Versions (showing 5 of 5)

Version Deps Published
3.0.6 2 / 5
3.0.5 2 / 5
3.0.3 2 / 5
3.0.1 2 / 5
3.0.0 2 / 5

v3.0.6

1 finding
LOW No provenance attestation provenance

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

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.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.

v3.0.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.