@augment-vir/test
A universal testing suite that works with Mocha style test runners _and_ Node.js's built-in test runner.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package in established augment-vir monorepo; 'test' substring match is not impersonation of jest. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped package in established augment-vir monorepo; not related to next.js. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped package in established augment-vir monorepo; 'test' substring match is not impersonation of vitest. | ai |
Versions (showing 51 of 99)
| Version | Deps | Published |
|---|---|---|
| 31.71.2 | 5 / 17 | |
| 31.71.1 | 5 / 17 | |
| 31.71.0 | 5 / 17 | |
| 31.70.1 | 5 / 17 | |
| 31.70.0 | 5 / 17 | |
| 31.69.0 | 5 / 17 | |
| 31.68.4 | 5 / 17 | |
| 31.68.3 | 5 / 17 | |
| 31.68.2 | 5 / 17 | |
| 31.68.1 | 5 / 17 | |
| 31.68.0 | 5 / 17 | |
| 31.67.1 | 5 / 17 | |
| 31.67.0 | 5 / 17 | |
| 31.66.0 | 5 / 17 | |
| 31.65.0 | 5 / 17 | |
| 31.64.1 | 5 / 17 | |
| 31.64.0 | 5 / 17 | |
| 31.63.0 | 5 / 16 | |
| 31.62.0 | 5 / 16 | |
| 31.61.0 | 5 / 16 | |
| 31.60.0 | 5 / 16 | |
| 31.59.3 | 5 / 16 | |
| 31.59.2 | 5 / 16 | |
| 31.59.1 | 5 / 16 | |
| 31.59.0 | 5 / 16 | |
| 31.58.0 | 5 / 16 | |
| 31.57.5 | 5 / 16 | |
| 31.57.4 | 5 / 16 | |
| 31.57.3 | 5 / 16 | |
| 31.57.2 | 5 / 16 | |
| 31.57.1 | 5 / 16 | |
| 31.57.0 | 5 / 16 | |
| 31.56.0 | 5 / 16 | |
| 31.55.0 | 5 / 16 | |
| 31.54.4 | 5 / 16 | |
| 31.54.3 | 6 / 15 | |
| 31.54.2 | 5 / 15 | |
| 31.54.1 | 5 / 15 | |
| 31.54.0 | 5 / 15 | |
| 31.53.0 | 5 / 15 | |
| 31.52.0 | 5 / 15 | |
| 31.51.1 | 5 / 15 | |
| 31.51.0 | 5 / 15 | |
| 31.50.4 | 5 / 15 | |
| 31.50.3 | 5 / 15 | |
| 31.50.2 | 5 / 15 | |
| 31.50.1 | 5 / 15 | |
| 31.50.0 | 5 / 15 | |
| 31.49.0 | 5 / 9 | |
| 31.48.0 | 5 / 9 | |
| 31.47.0 | 5 / 9 |
v31.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.69.0
2 findingsPackage name '@augment-vir/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.68.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.68.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.67.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.59.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.59.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.59.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.57.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.57.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.57.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.57.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.57.0
2 findingsPackage name '@augment-vir/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.54.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.50.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.50.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.50.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.