← Home

jasminum

npm Repository Homepage

A light, modular, promissory, isomorphic Jasmine test scaffold clone

15
Versions
BSD-3-Clause
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

kriskowal

Keywords

jasminetesttestingbddpromiseisomorphic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:scripts/saucelabs.js AI (source-diff): scripts/saucelabs.js is a CI integration script for SauceLabs browser testing, reading credentials from env vars. Not a dropper — only runs via explicit npm run saucelabs, not on install. ai
npm-metadata suspicious-initial-version AI (npm-metadata): kriskowal intentionally uses 0.0.0 versioning for scaffold/experimental packages; this is a 12-year-old package with 15 versions, not a throwaway malicious package. ai
phantom-deps phantom-dep:wd AI (phantom-deps): wd is used in test/sauce.js for WebDriver-based Sauce Labs testing; not imported in main library code but legitimately used in test infrastructure. ai
source-diff net-exec-file:test/sauce.js AI (source-diff): test/sauce.js is a CI test helper for Sauce Labs browser testing using standard SDKs and env-var credentials. Not a dropper; only invoked via test:sauce script, never at install time. ai
phantom-deps phantom-dep:knox AI (phantom-deps): knox is used in test/sauce.js for S3 uploads of test artifacts; legitimately used in test infrastructure. ai
phantom-deps phantom-dep:saucelabs AI (phantom-deps): saucelabs SDK is used in test/sauce.js for CI browser testing; legitimately used in test infrastructure. ai
semgrep semgrep:child-process-spawn AI (semgrep): Spawning phantomjs is the explicit purpose of phantom/runner.js; this is not malicious use of child_process. ai
semgrep semgrep:child-process-import AI (semgrep): jasminum-phantom binary intentionally spawns PhantomJS as its core function; child_process use is expected and documented. ai
semgrep semgrep:dynamic-require AI (semgrep): Test runners must dynamically require user-specified test files at runtime; this is inherent to the tool's design. ai

Versions (showing 15 of 15)

Version Deps Published
2.0.7 17 / 0
2.0.6 17 / 0
2.0.5 14 / 0
2.0.4 11 / 0
2.0.3 11 / 0
2.0.2 11 / 0
2.0.1 10 / 0
2.0.0 10 / 0
0.0.6 14 / 1
0.0.5 14 / 1
0.0.4 11 / 0
0.0.3 11 / 0
0.0.2 10 / 0
0.0.1 9 / 0
0.0.0 5 / 1

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

2 findings
HIGH New file with network + code execution: scripts/saucelabs.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

3 findings
HIGH Publisher changed: kriskowal → hthetiot (on 2018-03-06) provenance

This version was published by a different npm account than previous versions on 2018-03-06. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: test/sauce.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

1 finding
LOW No provenance attestation provenance

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

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