jssip
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is confined to gulpfile.js (dev build tooling), not runtime library code. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): @types/* packages are TypeScript type declarations loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:@types/events | AI (phantom-deps): @types/* packages are TypeScript type declarations loaded by convention, not direct imports. | ai |
Versions (showing 87 of 87)
| Version | Deps | Published |
|---|---|---|
| 3.13.8 | 3 / 21 | |
| 3.13.7 | 3 / 21 | |
| 3.13.6 | 3 / 21 | |
| 3.13.5 | 3 / 21 | |
| 3.13.4 | 3 / 21 | |
| 3.13.2 | 3 / 21 | |
| 3.13.0 | 3 / 21 | |
| 3.12.0 | 3 / 10 | |
| 3.11.1 | 5 / 5 | |
| 3.11.0 | 5 / 9 | |
| 3.10.10 | 5 / 18 | |
| 3.10.9 | 5 / 18 | |
| 3.10.7 | 5 / 18 | |
| 3.10.6 | 5 / 18 | |
| 3.10.5 | 5 / 18 | |
| 3.10.4 | 5 / 18 | |
| 3.10.3 | 5 / 18 | |
| 3.10.2 | 5 / 18 | |
| 3.10.1 | 5 / 18 | |
| 3.10.0 | 5 / 18 | |
| 3.9.4 | 5 / 18 | |
| 3.9.3 | 5 / 18 | |
| 3.9.2 | 5 / 18 | |
| 3.9.1 | 5 / 18 | |
| 3.9.0 | 5 / 18 | |
| 3.8.2 | 5 / 18 | |
| 3.8.1 | 5 / 18 | |
| 3.8.0 | 5 / 18 | |
| 3.7.11 | 5 / 18 | |
| 3.7.10 | 5 / 18 | |
| 3.7.9 | 5 / 18 | |
| 3.7.8 | 5 / 18 | |
| 3.7.7 | 5 / 18 | |
| 3.7.6 | 5 / 18 | |
| 3.7.5 | 5 / 18 | |
| 3.7.4 | 5 / 18 | |
| 3.7.3 | 5 / 18 | |
| 3.7.2 | 5 / 18 | |
| 3.7.1 | 5 / 18 | |
| 3.7.0 | 5 / 18 | |
| 3.6.3 | 5 / 18 | |
| 3.6.2 | 5 / 18 | |
| 3.6.1 | 5 / 18 | |
| 3.6.0 | 5 / 18 | |
| 3.5.11 | 5 / 18 | |
| 3.5.10 | 5 / 18 | |
| 3.5.9 | 6 / 18 | |
| 3.5.8 | 5 / 18 | |
| 3.5.7 | 5 / 18 | |
| 3.5.6 | 5 / 18 | |
| 3.5.5 | 5 / 18 | |
| 3.5.4 | 5 / 18 | |
| 3.5.3 | 5 / 18 | |
| 3.5.2 | 5 / 18 | |
| 3.5.1 | 5 / 18 | |
| 3.5.0 | 5 / 18 | |
| 3.4.6 | 3 / 18 | |
| 3.4.5 | 3 / 18 | |
| 3.4.4 | 3 / 18 | |
| 3.4.3 | 3 / 18 | |
| 3.4.2 | 3 / 18 | |
| 3.4.1 | 3 / 18 | |
| 3.4.0 | 3 / 18 | |
| 3.3.11 | 3 / 18 | |
| 3.3.10 | 3 / 18 | |
| 3.3.9 | 3 / 18 | |
| 3.3.8 | 3 / 18 | |
| 3.3.7 | 3 / 18 | |
| 3.3.6 | 3 / 18 | |
| 3.3.5 | 3 / 18 | |
| 3.3.4 | 3 / 18 | |
| 3.3.3 | 3 / 18 | |
| 3.3.2 | 3 / 18 | |
| 3.3.1 | 4 / 17 | |
| 3.3.0 | 4 / 17 | |
| 3.2.17 | 4 / 17 | |
| 3.2.16 | 4 / 17 | |
| 3.2.15 | 3 / 18 | |
| 3.2.14 | 4 / 18 | |
| 3.2.13 | 4 / 18 | |
| 3.2.12 | 4 / 18 | |
| 3.2.11 | 4 / 18 | |
| 3.2.10 | 4 / 18 | |
| 3.2.7 | 3 / 18 | |
| 3.2.5 | 3 / 18 | |
| 3.2.4 | 3 / 18 | |
| 3.2.2 | 3 / 18 |
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2021-06-01, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.7.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2021-04-12, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.7.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2021-03-26, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.7.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2021-03-18, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2020-12-15, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2020-10-23, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2020-10-14, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2020-08-14, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2020-08-13, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2020-07-29, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2020-07-24, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2020-07-09, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2020-06-01, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2020-05-13, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2019-08-12, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2019-01-02, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2018-12-18, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2018-10-11, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2018-09-17, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2018-06-03, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ibc) than the most recent previously approved version (jmillan) on 2018-03-23, but ibc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2018-03-06, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmillan) than the most recent previously approved version (ibc) on 2018-01-19, but jmillan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.