jstat
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:jstat-1.9.5/test/models/thousand-size-test.js | AI (source-diff): Long lines are inline numeric test datasets, not obfuscation. | ai | |
| source-diff | obfuscated-file:jstat-1.9.5/test/models/simple-regression-test.js | AI (source-diff): Long lines are inline numeric test datasets, not obfuscation. | ai | |
| source-diff | net-exec-file:jstat-1.9.5/doc/assets/sh_main.js | AI (source-diff): SHJS syntax-highlighter doc asset; eval targets AJAX-loaded language defs, not runtime. | ai | |
| source-diff | obfuscated-file:jstat-1.9.3/test/models/thousand-size-test.js | AI (source-diff): Inline numeric test data arrays; benign test fixture. | ai | |
| source-diff | obfuscated-file:jstat-1.9.3/test/models/simple-regression-test.js | AI (source-diff): Long lines are inline numeric regression datasets in test fixtures, not obfuscation. | ai | |
| source-diff | net-exec-file:jstat-1.9.3/doc/assets/sh_main.js | AI (source-diff): Vendored SHJS syntax highlighter doc asset; not part of runtime. | ai | |
| phantom-deps | phantom-dep:vows | AI (phantom-deps): Test framework referenced only via npm test script. | ai | |
| npm-metadata | url-dep:vows | AI (npm-metadata): Legacy test-only dependency, unchanged for years, not part of runtime. | ai | |
| phantom-deps | phantom-dep:uglify-js | AI (phantom-deps): Build-time dev dependency, no runtime import expected. | ai | |
| source-diff | net-exec-file:jstat-1.9.0/doc/assets/sh_main.js | AI (source-diff): Vendored SHJS syntax highlighter doc asset; benign. | ai | |
| source-diff | obfuscated-file:jstat-1.9.0/test/models/thousand-size-test.js | AI (source-diff): Long lines are numeric test fixtures, not obfuscation. | ai | |
| source-diff | obfuscated-file:jstat-1.9.0/test/models/simple-regression-test.js | AI (source-diff): Long lines are regression test data arrays, not obfuscated code. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in doc/assets/sh_main.js, a documentation-only syntax highlighter asset, not in the distributed library code. Not reachable by consumers of the package. | ai | |
| provenance | no-provenance | AI (provenance): Established package (4014 days old); lack of Sigstore provenance is common and not a risk indicator here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.9.6 | 0 / 2 | |
| 1.9.5 | 0 / 2 | |
| 1.9.4 | 0 / 2 | |
| 1.9.3 | 0 / 2 | |
| 1.9.2 | 0 / 2 | |
| 1.9.1 | 0 / 2 | |
| 1.9.0 | 0 / 2 | |
| 1.8.3 | 0 / 2 | |
| 1.8.2 | 0 / 2 | |
| 1.8.1 | 0 / 2 | |
| 1.8.0 | 0 / 2 | |
| 1.7.2 | 0 / 2 | |
| 1.7.1 | 0 / 2 | |
| 1.7.0 | 0 / 2 | |
| 1.6.3 | 0 / 2 | |
| 1.6.2 | 0 / 2 | |
| 1.6.1 | 0 / 2 | |
| 1.6.0 | 0 / 2 | |
| 1.5.3 | 0 / 2 | |
| 1.5.2 | 0 / 2 | |
| 1.1.5 | 2 / 0 |
v1.9.5
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trev.norris.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trev.norris.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trev.norris.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.