@jsii/spec
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:lib/validators.js | AI (source-diff): validators.js is an esbuild-bundled AJV JSON schema validator. ajv moved from runtime dep to devDep and is bundled via esbuild. Minified lines are expected build output, not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is fully explained by bundling AJV into validators.js via esbuild, replacing the runtime dependency. This is a legitimate architectural change. | ai |
Versions (showing 51 of 159)
| Version | Deps | Published |
|---|---|---|
| 1.139.0 | 0 / 7 | |
| 1.138.0 | 0 / 7 | |
| 1.137.0 | 0 / 7 | |
| 1.136.0 | 0 / 7 | |
| 1.135.0 | 0 / 7 | |
| 1.134.0 | 0 / 7 | |
| 1.133.0 | 0 / 7 | |
| 1.132.0 | 0 / 7 | |
| 1.131.0 | 0 / 7 | |
| 1.130.0 | 0 / 7 | |
| 1.129.0 | 0 / 7 | |
| 1.128.0 | 0 / 7 | |
| 1.127.0 | 0 / 4 | |
| 1.126.0 | 1 / 3 | |
| 1.125.0 | 1 / 3 | |
| 1.124.0 | 1 / 3 | |
| 1.123.0 | 1 / 3 | |
| 1.122.0 | 1 / 3 | |
| 1.121.0 | 1 / 3 | |
| 1.120.0 | 1 / 3 | |
| 1.119.0 | 1 / 3 | |
| 1.118.0 | 1 / 3 | |
| 1.117.0 | 1 / 3 | |
| 1.116.0 | 1 / 3 | |
| 1.115.0 | 1 / 3 | |
| 1.114.1 | 1 / 3 | |
| 1.113.0 | 1 / 3 | |
| 1.112.0 | 1 / 3 | |
| 1.111.0 | 1 / 3 | |
| 1.110.0 | 1 / 3 | |
| 1.109.0 | 1 / 3 | |
| 1.108.0 | 1 / 3 | |
| 1.107.0 | 1 / 3 | |
| 1.106.0 | 1 / 3 | |
| 1.105.0 | 1 / 3 | |
| 1.104.0 | 1 / 3 | |
| 1.103.1 | 1 / 3 | |
| 1.103.0 | 1 / 3 | |
| 1.102.0 | 1 / 3 | |
| 1.101.0 | 1 / 3 | |
| 1.100.0 | 1 / 3 | |
| 1.99.0 | 1 / 3 | |
| 1.98.0 | 1 / 3 | |
| 1.97.0 | 1 / 3 | |
| 1.96.0 | 1 / 3 | |
| 1.95.0 | 1 / 3 | |
| 1.94.0 | 1 / 3 | |
| 1.93.0 | 1 / 3 | |
| 1.92.0 | 1 / 3 | |
| 1.91.0 | 1 / 3 | |
| 1.90.0 | 1 / 3 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.