jsii
[](https://cdk.dev) [: downlevel-dts is a legitimate TS declaration tool; its use in jsii's build pipeline is expected and stable. | ai | |
| provenance | no-provenance | AI (provenance): Established AWS package with strong publisher track record; lack of Sigstore provenance is a process gap, not a security risk for this well-known package. | ai | |
| dependencies | unvetted-dep:sort-json | AI (dependencies): sort-json is a small, well-known utility package with no security concerns; appropriate dependency for a compiler tool. | ai | |
| phantom-deps | phantom-dep:semver-intersect | AI (phantom-deps): semver-intersect is a declared runtime dependency used internally; phantom-dep finding is a false positive for this package. | ai | |
| dependencies | unvetted-dep:semver-intersect | AI (dependencies): semver-intersect is a legitimate semver utility; appropriate for jsii's version constraint handling. | ai | |
| dependencies | unvetted-dep:@jsii/spec | AI (dependencies): @jsii/spec is a first-party AWS/jsii package, a stable sibling dependency of jsii itself. Safe for all versions of this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): jsii is a canonical AWS CDK multi-language compiler, not a typosquat of joi. Name similarity is purely coincidental; package predates the concern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in a test/verification script reading package.json files from a directory — benign test infrastructure, not production arbitrary module loading. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 5.9.44 | 12 / 33 | |
| 5.9.43 | 12 / 33 | |
| 5.9.42 | 12 / 33 | |
| 5.9.41 | 12 / 33 | |
| 5.9.40 | 12 / 33 | |
| 5.9.39 | 12 / 33 | |
| 5.9.37 | 12 / 33 | |
| 5.9.36 | 12 / 33 | |
| 5.9.35 | 12 / 33 | |
| 5.9.34 | 12 / 33 | |
| 5.9.33 | 12 / 33 | |
| 5.9.32 | 12 / 33 | |
| 5.9.31 | 12 / 33 | |
| 5.9.30 | 12 / 33 | |
| 5.9.29 | 12 / 33 | |
| 5.9.28 | 12 / 33 | |
| 5.9.27 | 12 / 33 | |
| 5.9.26 | 12 / 33 | |
| 5.9.25 | 12 / 33 | |
| 5.9.24 | 12 / 33 | |
| 5.9.23 | 12 / 33 | |
| 5.9.22 | 12 / 33 | |
| 5.9.21 | 12 / 33 | |
| 5.9.20 | 12 / 33 | |
| 5.9.19 | 12 / 33 | |
| 5.9.18 | 12 / 33 | |
| 5.9.14 | 12 / 33 | |
| 5.9.13 | 12 / 33 | |
| 5.9.12 | 12 / 33 | |
| 5.9.11 | 12 / 33 | |
| 5.9.10 | 12 / 33 | |
| 5.9.9 | 12 / 33 | |
| 5.9.8 | 12 / 33 | |
| 5.9.7 | 12 / 33 | |
| 5.9.6 | 12 / 33 | |
| 5.9.5 | 12 / 33 | |
| 5.9.4 | 12 / 33 | |
| 5.9.3 | 12 / 33 | |
| 5.9.2 | 12 / 33 | |
| 5.9.1 | 12 / 33 | |
| 5.9.0 | 12 / 33 | |
| 5.8.27 | 12 / 33 | |
| 5.8.26 | 12 / 33 | |
| 5.8.25 | 12 / 33 | |
| 5.8.22 | 12 / 33 | |
| 5.8.21 | 12 / 33 | |
| 5.8.20 | 12 / 33 | |
| 5.8.19 | 12 / 33 | |
| 5.8.18 | 12 / 33 | |
| 5.8.17 | 12 / 33 | |
| 5.8.16 | 12 / 33 |
v5.9.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.