@diia-inhouse/diia-app SEE LICENSE IN LICENSE.md 27 versions

@diia-inhouse/diia-app

npm Repository Homepage

Application package with IoC container

27

Versions

SEE LICENSE IN LICENSE.md

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

diia-open-source

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): IoC container loads logger by configurable package name; stable plugin-loader pattern for this framework.	ai	2026/04/29
semgrep	semgrep:base64-decode	AI (semgrep): Decodes gRPC metadata session field — standard transport encoding, not payload obfuscation.	ai	2026/04/29
phantom-deps	phantom-dep:ts-patch	AI (phantom-deps): ts-patch is a build-time tool invoked via prepare script, not imported directly.	ai	2026/04/29
phantom-deps	phantom-dep:nats	AI (phantom-deps): nats is a runtime transport dep used by moleculer; loaded by convention, not direct import.	ai	2026/04/29
phantom-deps	phantom-dep:@types/dotenv-flow	AI (phantom-deps): Type-only package; never directly imported, used at compile time.	ai	2026/04/29
phantom-deps	phantom-dep:@opentelemetry/core	AI (phantom-deps): OpenTelemetry core loaded transitively by auto-instrumentation; not directly imported by design.	ai	2026/04/29

Versions (showing 27 of 27)

Version	Deps	Published
33.0.3	27 / 36	2026-06-12
33.0.2	27 / 36	2026-06-07
33.0.1	27 / 36	2026-06-03
33.0.0	27 / 36	2026-05-27
32.4.0	27 / 36	2026-05-25
31.9.10	27 / 36	2026-05-04
31.9.7	27 / 36	2026-04-29
31.9.6	27 / 36	2026-04-28
31.9.5	27 / 36	2026-04-27
31.9.4	27 / 36	2026-04-24
31.9.3	27 / 36	2026-04-22
31.8.5	27 / 36	2026-04-17
31.8.4	27 / 36	2026-04-13
31.8.3	27 / 36	2026-04-13
31.8.2	27 / 36	2026-04-03
31.8.1	27 / 36	2026-04-02
31.8.0	27 / 36	2026-04-02
31.7.0	27 / 36	2026-04-01
31.6.0	27 / 36	2026-04-01
31.5.1	27 / 36	2026-03-30
31.5.0	27 / 36	2026-03-27
31.4.0	27 / 36	2026-03-27
31.3.0	27 / 36	2026-03-20
31.2.2	27 / 36	2026-03-18
31.2.1	27 / 36	2026-03-16
31.2.0	27 / 36	2026-03-13
31.1.1	27 / 36	2026-03-05

v33.0.3

1 finding

LOW No provenance attestation provenance

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

v33.0.2

1 finding

LOW No provenance attestation provenance

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

v33.0.1

1 finding

LOW No provenance attestation provenance

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

v33.0.0

1 finding

LOW No provenance attestation provenance

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

v32.4.0

1 finding

LOW No provenance attestation provenance

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

v31.9.10

1 finding

LOW No provenance attestation provenance

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

v31.9.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.

v31.9.5

1 finding

LOW No provenance attestation provenance

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

v31.9.4

1 finding

LOW No provenance attestation provenance

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

v31.9.3

1 finding

LOW No provenance attestation provenance

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

v31.8.5

1 finding

LOW No provenance attestation provenance

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

v31.8.4

1 finding

LOW No provenance attestation provenance

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

v31.8.3

1 finding

LOW No provenance attestation provenance

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

v31.8.2

1 finding

LOW No provenance attestation provenance

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

v31.8.1

1 finding

LOW No provenance attestation provenance

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

v31.8.0

1 finding

LOW No provenance attestation provenance

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

v31.7.0

1 finding

LOW No provenance attestation provenance

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

v31.6.0

1 finding

LOW No provenance attestation provenance

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

v31.5.1

1 finding

LOW No provenance attestation provenance

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

v31.5.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.

v31.4.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.

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

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

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

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

v31.1.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.