opentracing
[![Build Status][ci-img]][ci] [![Coverage Status][cov-img]][cov] [![NPM Published Version][npm-img]][npm] ![Node Version][node-img] [ relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/prettify.js | AI (source-diff): Google code-prettify bundled with Istanbul coverage reports; standard minified library, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/opentracing-node.js | AI (source-diff): Webpack bundle output of the opentracing library source; expected build artifact per package.json scripts. | ai | |
| provenance | publisher-changed | AI (provenance): bcronin is a long-standing maintainer of opentracing (3681 days, all 40 versions). Legitimate transition from bensigelman within the same project. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2018, before Sigstore provenance existed. Expected for this era of packages. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.14.7 | 0 / 20 | |
| 0.14.6 | 0 / 20 | |
| 0.14.5 | 0 / 20 | |
| 0.14.4 | 0 / 20 | |
| 0.14.3 | 0 / 19 | |
| 0.14.2 | 0 / 21 | |
| 0.14.1 | 0 / 21 | |
| 0.14.0 | 0 / 21 | |
| 0.13.0 | 0 / 39 | |
| 0.12.1 | 0 / 39 | |
| 0.11.1 | 0 / 35 | |
| 0.10.7 | 0 / 35 | |
| 0.10.6 | 0 / 35 | |
| 0.10.5 | 0 / 35 | |
| 0.10.4 | 0 / 35 | |
| 0.10.3 | 0 / 35 | |
| 0.10.2 | 0 / 35 | |
| 0.10.1 | 0 / 35 | |
| 0.9.18 | 0 / 30 | |
| 0.9.17 | 0 / 30 | |
| 0.9.16 | 0 / 30 | |
| 0.9.15 | 0 / 30 | |
| 0.9.14 | 0 / 30 | |
| 0.9.13 | 0 / 14 | |
| 0.9.12 | 0 / 14 | |
| 0.9.11 | 0 / 14 | |
| 0.9.10 | 0 / 14 | |
| 0.9.9 | 0 / 14 | |
| 0.9.7 | 0 / 14 | |
| 0.9.6 | 0 / 14 | |
| 0.9.5 | 0 / 14 | |
| 0.9.4 | 0 / 14 | |
| 0.9.3 | 0 / 14 | |
| 0.9.2 | 0 / 14 | |
| 0.9.1 | 0 / 14 | |
| 0.9.0 | 0 / 14 | |
| 0.1.3 | 1 / 14 | |
| 0.1.2 | 1 / 14 | |
| 0.1.1 | 1 / 14 | |
| 0.1.0 | 1 / 14 |
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-06. This could indicate a legitimate maintainer transition or an account compromise.
v0.14.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.14.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-06. This could indicate a legitimate maintainer transition or an account compromise.
v0.14.2
2 findingsThis version was published by a different npm account than previous versions on 2018-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.13.0
4 findingsNewly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.12.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-07-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-07-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-25. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.