@telorun/test
Telo Test module - Test runner for Telo manifests.
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 @telorun/test is a test runner for the Telo platform, not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped package under telorun org; no resemblance to Next.js in purpose or namespace. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped package under telorun org; not impersonating vitest. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Test runner merging .env files with process.env is expected behavior for this package's purpose. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 2 / 2 | |
| 1.0.4 | 2 / 2 | |
| 1.0.3 | 2 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 0.4.12 | 2 / 3 | |
| 0.4.11 | 2 / 3 | |
| 0.4.10 | 2 / 3 | |
| 0.4.9 | 2 / 3 | |
| 0.4.8 | 2 / 3 | |
| 0.4.7 | 2 / 3 | |
| 0.4.6 | 2 / 3 | |
| 0.4.5 | 2 / 3 | |
| 0.4.4 | 2 / 3 | |
| 0.4.3 | 2 / 3 | |
| 0.4.2 | 2 / 3 | |
| 0.4.1 | 2 / 3 | |
| 0.4.0 | 2 / 2 | |
| 0.3.10 | 3 / 2 | |
| 0.3.9 | 3 / 2 | |
| 0.3.8 | 3 / 2 | |
| 0.3.7 | 3 / 2 | |
| 0.3.6 | 3 / 2 | |
| 0.3.5 | 3 / 2 | |
| 0.3.4 | 3 / 2 | |
| 0.3.3 | 3 / 2 | |
| 0.3.2 | 3 / 2 | |
| 0.3.1 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.3 | 3 / 2 | |
| 0.1.2 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.1.0 | 3 / 2 |
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
3 findingsPackage name '@telorun/test' is 1 edit(s) away from popular package 'jest'.
Spreading entire process.env into an object — may capture all secrets 153 | const base = parseEnvFile(tryReadFile(path.join(dir, ".env"))); 154 | const local = parseEnvFile(tryReadFile(path.join(dir, ".env.local"))); > 155 | return { ...base, ...local, ...process.env }; 156 | } 157 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
3 findingsPackage name '@telorun/test' is 1 edit(s) away from popular package 'jest'.
Spreading entire process.env into an object — may capture all secrets 134 | const base = parseEnvFile(tryReadFile(path.join(dir, ".env"))); 135 | const local = parseEnvFile(tryReadFile(path.join(dir, ".env.local"))); > 136 | return { ...base, ...local, ...process.env }; 137 | } 138 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.