@diia-inhouse/test SEE LICENCE IN LICENCE.md 37 versions

@diia-inhouse/test

npm Repository Homepage

test-utils

37

Versions

SEE LICENCE IN LICENCE.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
source-diff	obfuscated-file:dist/stubs/photo.js	AI (source-diff): Long line is a Base64-encoded PNG image used as a test stub, not obfuscated malicious code.	ai	2026/05/22
typosquat	typosquat.levenshtein:jest	AI (typosquat): @diia-inhouse/test is a scoped package from Ukraine's official Diia gov-tech org; the name reflects its purpose, not impersonation of jest. Stable false positive for this package.	ai	2026/04/25
typosquat	typosquat.levenshtein:next	AI (typosquat): Scoped @diia-inhouse namespace with 688-day history and GitHub repo; no relation to next.js. Stable false positive.	ai	2026/04/25
typosquat	typosquat.levenshtein:vitest	AI (typosquat): Package legitimately wraps vitest as a test utility; the name similarity is intentional and descriptive, not a typosquat. Stable false positive.	ai	2026/04/25
dependencies	unvetted-dep:@diia-inhouse/design-system	AI (dependencies): Intra-org dependency from the same @diia-inhouse namespace; expected for Diia ecosystem packages.	ai	2026/04/25

Versions (showing 37 of 37)

Version	Deps	Published
8.2.6	9 / 16	2026-06-04
8.2.5	9 / 16	2026-06-03
8.2.4	9 / 16	2026-05-29
8.2.3	9 / 16	2026-05-28
8.2.2	9 / 16	2026-05-27
8.2.1	9 / 16	2026-05-23
8.2.0	9 / 16	2026-05-21
8.1.4	9 / 16	2026-05-21
8.0.2	9 / 16	2026-05-15
8.0.1	9 / 16	2026-05-15
8.0.0	9 / 16	2026-05-15
7.3.24	9 / 12	2026-05-04
7.3.23	9 / 12	2026-05-01
7.3.21	9 / 12	2026-04-28
7.3.20	9 / 12	2026-04-28
7.3.19	9 / 12	2026-04-28
7.3.18	9 / 12	2026-04-25
7.3.17	9 / 12	2026-04-23
7.3.16	9 / 12	2026-04-18
7.3.15	9 / 12	2026-04-17
7.3.14	9 / 12	2026-04-16
7.3.13	9 / 12	2026-04-14
7.3.12	9 / 12	2026-04-11
7.3.11	9 / 12	2026-04-09
7.3.10	9 / 12	2026-04-08
7.3.9	9 / 12	2026-04-07
7.3.8	9 / 12	2026-04-06
7.3.7	9 / 12	2026-04-05
7.3.6	9 / 12	2026-04-03
7.3.5	9 / 12	2026-03-30
7.3.4	9 / 12	2026-03-25
7.3.3	9 / 12	2026-03-21
7.3.2	9 / 12	2026-03-20
7.3.1	9 / 12	2026-03-14
7.3.0	9 / 12	2026-03-10
7.2.1	9 / 12	2026-03-12
7.2.0	9 / 12	2026-02-27

v8.2.6

1 finding

LOW No provenance attestation provenance

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

v8.2.5

1 finding

LOW No provenance attestation provenance

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

v8.2.4

1 finding

LOW No provenance attestation provenance

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

v8.2.3

1 finding

LOW No provenance attestation provenance

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

v8.2.2

1 finding

LOW No provenance attestation provenance

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

v8.2.1

1 finding

LOW No provenance attestation provenance

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

v8.2.0

2 findings

HIGH New obfuscated file: dist/stubs/photo.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v8.1.4

2 findings

HIGH New obfuscated file: dist/stubs/photo.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v8.0.2

1 finding

LOW No provenance attestation provenance

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

v8.0.1

1 finding

LOW No provenance attestation provenance

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

v8.0.0

1 finding

LOW No provenance attestation provenance

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

v7.3.24

1 finding

LOW No provenance attestation provenance

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

v7.3.23

1 finding

LOW No provenance attestation provenance

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

v7.3.20

1 finding

LOW No provenance attestation provenance

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

v7.3.19

1 finding

LOW No provenance attestation provenance

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

v7.3.18

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@diia-inhouse/test' is 1 edit(s) away from popular package 'jest'.

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.

v7.3.17

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.

v7.3.16

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.

v7.3.15

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.

v7.3.14

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.

v7.3.13

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.

v7.3.12

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.

v7.3.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.

v7.3.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.

v7.3.9

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.

v7.3.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.

v7.3.7

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.

v7.3.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.

v7.3.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.

v7.3.4

1 finding

LOW No provenance attestation provenance

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

v7.3.3

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.

v7.3.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.

v7.3.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.

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

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

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