@virmator/test No license 25 versions

@virmator/test

npm Repository Homepage

25

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

electrovir

Keywords

virmatortestnodewebbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Publisher has 305 approved packages and 0 rejections; dormancy is plausible for a monorepo plugin, not a takeover indicator.	ai	2026/05/17
typosquat	typosquat.levenshtein:jest	AI (typosquat): Scoped package in established virmator monorepo; not a typosquat of jest.	ai	2026/05/11
typosquat	typosquat.levenshtein:next	AI (typosquat): Scoped package in established virmator monorepo; not a typosquat of next.	ai	2026/05/11
typosquat	typosquat.levenshtein:vitest	AI (typosquat): Scoped package in established virmator monorepo; not a typosquat of vitest.	ai	2026/05/11
phantom-deps	phantom-dep:@web/dev-server-core	AI (phantom-deps): Used in config files as documented; stable false positive for this package.	ai	2026/05/11

Versions (showing 25 of 25)

Version	Deps	Published
14.19.0	13 / 13	2026-05-27
14.18.0	13 / 13	2026-05-26
14.17.1	13 / 13	2026-05-25
14.17.0	13 / 13	2026-05-25
14.16.0	13 / 13	2026-05-20
14.15.0	13 / 13	2026-05-16
14.14.2	13 / 13	2026-05-10
14.14.1	13 / 13	2026-05-10
14.13.1	13 / 13	2026-05-05
14.13.0	13 / 13	2026-05-05
14.12.2	13 / 13	2026-04-15
14.10.3	13 / 13	2026-03-27
14.8.2	13 / 13	2026-03-07
14.7.2	13 / 13	2026-03-01
14.7.0	13 / 13	2026-02-28
14.3.5	10 / 13	2025-12-18
14.2.2	10 / 13	2025-11-09
14.2.1	10 / 13	2025-10-26
14.2.0	10 / 13	2025-10-25
14.1.0	10 / 13	2025-10-01
14.0.4	10 / 13	2025-09-16
14.0.3	10 / 13	2025-09-05
14.0.2	10 / 13	2025-09-01
14.0.1	10 / 13	2025-08-21
14.0.0	10 / 13	2025-08-21

v14.19.0

1 finding

LOW No provenance attestation provenance

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

v14.18.0

1 finding

LOW No provenance attestation provenance

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

v14.17.1

1 finding

LOW No provenance attestation provenance

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

v14.17.0

1 finding

LOW No provenance attestation provenance

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

v14.16.0

1 finding

LOW No provenance attestation provenance

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

v14.15.0

1 finding

LOW No provenance attestation provenance

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

v14.14.2

2 findings

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

Package name '@virmator/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.

v14.14.1

2 findings

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

Package name '@virmator/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.

v14.13.1

2 findings

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

Package name '@virmator/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.

v14.13.0

2 findings

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

Package name '@virmator/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.

v14.12.2

2 findings

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

Package name '@virmator/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.

v14.10.3

2 findings

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

Package name '@virmator/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.

v14.8.2

1 finding

LOW No provenance attestation provenance

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

v14.7.2

1 finding

LOW No provenance attestation provenance

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

v14.7.0

2 findings

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

Package name '@virmator/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.

v14.3.5

2 findings

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

Package name '@virmator/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.

v14.2.2

1 finding

LOW No provenance attestation provenance

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

v14.2.1

1 finding

LOW No provenance attestation provenance

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

v14.2.0

1 finding

LOW No provenance attestation provenance

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

v14.1.0

1 finding

LOW No provenance attestation provenance

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

v14.0.4

1 finding

LOW No provenance attestation provenance

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

v14.0.3

1 finding

LOW No provenance attestation provenance

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

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

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

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