@browserstack/ai-sdk-node
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires inside obfuscated bundle; no concrete hostile target. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid referenced in config; stable FP. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal early release under legit scoped @browserstack org; spam heuristics are false positives here. | ai | |
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): Vendor ships obfuscated dist for this scoped SDK; structural and unchanged across versions. | ai |
v1.5.9
2 findings[Reject — re-review on republish] (prior reject: AI (semgrep): Entire index.js is obfuscated; this is a structural property of the package, not a one-off pattern.) while(!![]) loop is a signature of javascript-obfuscator output > 1 | 'use strict';const a0_0x1508e3=a0_0xf4be;(function(_0x491f8f,_0x1b6b9c){const _0x4e5b9d=a0_0xf4be,_0x225668=_0x491f8f();
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsMatched 6 signal(s), weighted score 7: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 0 code file(s), 120 bytes total. • [S_INFLATED_FIRST_SEMVER] First publish at version 1.0.1 — inflated semver on a brand-new package.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.