@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 — the axios compromise (March 2026) 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: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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.129.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.126.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.125.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.124.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.123.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.122.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.119.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.118.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.114.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.113.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.