jsii-diff
Assembly comparison for jsii
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:child-process-import | AI (semgrep): CLI tool legitimately spawns npm subprocesses; stable pattern across all versions of this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.139.0 | 6 / 9 | |
| 1.138.0 | 6 / 9 | |
| 1.137.0 | 6 / 9 | |
| 1.136.0 | 6 / 9 | |
| 1.135.0 | 6 / 9 | |
| 1.134.0 | 6 / 9 | |
| 1.133.0 | 6 / 9 | |
| 1.132.0 | 6 / 9 | |
| 1.131.0 | 6 / 9 | |
| 1.130.0 | 6 / 9 | |
| 1.129.0 | 6 / 9 | |
| 1.128.0 | 6 / 9 | |
| 1.127.0 | 6 / 6 | |
| 1.126.0 | 6 / 6 | |
| 1.125.0 | 6 / 6 | |
| 1.124.0 | 6 / 6 | |
| 1.123.0 | 6 / 6 | |
| 1.122.0 | 6 / 6 | |
| 1.121.0 | 6 / 6 | |
| 1.120.0 | 6 / 6 | |
| 1.119.0 | 6 / 6 | |
| 1.118.0 | 6 / 6 | |
| 1.117.0 | 6 / 6 | |
| 1.116.0 | 6 / 6 | |
| 1.115.0 | 6 / 6 | |
| 1.114.1 | 6 / 6 | |
| 1.113.0 | 6 / 5 | |
| 1.112.0 | 6 / 5 | |
| 1.111.0 | 6 / 5 | |
| 1.110.0 | 6 / 5 | |
| 1.109.0 | 6 / 5 | |
| 1.108.0 | 6 / 5 | |
| 1.107.0 | 6 / 5 | |
| 1.106.0 | 6 / 5 | |
| 1.105.0 | 6 / 5 | |
| 1.104.0 | 6 / 5 | |
| 1.103.1 | 6 / 5 | |
| 1.103.0 | 6 / 5 | |
| 1.102.0 | 6 / 5 | |
| 1.101.0 | 6 / 5 | |
| 1.100.0 | 6 / 5 | |
| 1.99.0 | 6 / 5 |
v1.139.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.110.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.