@diia-inhouse/db No license 17 versions

@diia-inhouse/db

npm Repository Homepage

17

Versions

—

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
dependencies	unvetted-dep:migrate-mongo	AI (dependencies): migrate-mongo is a well-known MongoDB migration tool; its use here is consistent with a DB utility package.	ai	2026/04/30
dependencies	unvetted-dep:@types/migrate-mongo	AI (dependencies): Type definitions package for migrate-mongo; no runtime risk.	ai	2026/04/30
phantom-deps	phantom-dep:pg	AI (phantom-deps): pg is a declared runtime dep used via config/convention in a DB abstraction package.	ai	2026/04/29
phantom-deps	phantom-dep:bson	AI (phantom-deps): bson is a declared runtime dep used via config in a MongoDB/Mongoose DB package.	ai	2026/04/29
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped org package @diia-inhouse/db; Levenshtein match to 'pg' is a false positive.	ai	2026/04/29
phantom-deps	phantom-dep:@types/migrate-mongo	AI (phantom-deps): Type-only package loaded by framework convention; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@diia-inhouse/validators	AI (phantom-deps): Same-org scoped package; used indirectly via shared utilities, stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:migrate-mongo	AI (phantom-deps): migrate-mongo loaded by convention/CLI in a DB migration utility package.	ai	2026/04/29
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped org package @diia-inhouse/db; Levenshtein match to 'qs' is a false positive.	ai	2026/04/29

Versions (showing 17 of 17)

Version	Deps	Published
12.3.2	15 / 26	2026-06-04
12.3.1	15 / 26	2026-05-26
12.3.0	15 / 26	2026-05-25
10.8.14	16 / 25	2026-05-03
10.8.12	16 / 25	2026-04-28
10.8.11	16 / 25	2026-04-27
10.8.10	16 / 25	2026-04-24
10.8.9	16 / 25	2026-04-23
10.8.8	16 / 25	2026-04-20
10.8.7	16 / 25	2026-04-13
10.8.6	16 / 25	2026-04-08
10.8.5	16 / 25	2026-04-05
10.8.4	16 / 25	2026-04-03
10.8.3	16 / 25	2026-03-23
10.8.2	16 / 25	2026-03-18
10.8.1	16 / 25	2026-03-05
10.8.0	16 / 25	2026-03-04

v12.3.2

1 finding

LOW No provenance attestation provenance

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

v12.3.1

1 finding

LOW No provenance attestation provenance

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

v12.3.0

1 finding

LOW No provenance attestation provenance

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

v10.8.14

1 finding

LOW No provenance attestation provenance

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

v10.8.11

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.

v10.8.10

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.

v10.8.9

1 finding

LOW No provenance attestation provenance

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

v10.8.8

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.

v10.8.7

1 finding

LOW No provenance attestation provenance

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

v10.8.6

1 finding

LOW No provenance attestation provenance

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

v10.8.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.

v10.8.4

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.

v10.8.3

1 finding

LOW No provenance attestation provenance

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

v10.8.2

1 finding

LOW No provenance attestation provenance

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

v10.8.1

1 finding

LOW No provenance attestation provenance

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

v10.8.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.