openapi3-ts
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/oas31-ebde447c.js | AI (source-diff): Content is standard Rollup/Vite minified bundle output for OpenAPI builder code — no obfuscation or malicious patterns present. Hash-named chunks are normal for this build toolchain. | ai | |
| source-diff | obfuscated-file:dist/oas30-14584a9c.js | AI (source-diff): Content is standard Rollup/Vite minified bundle output for OpenAPI builder code — no obfuscation or malicious patterns present. Hash-named chunks are normal for this build toolchain. | ai | |
| source-diff | obfuscated-file:dist/oas31-Dtl9zIuV.js | AI (source-diff): Minified Vite/Rollup build artifact of the openapi3-ts library. Content is recognizable OpenAPI builder logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/oas30-CAmzubQd.js | AI (source-diff): Minified Vite/Rollup build artifact of the openapi3-ts library. Content is recognizable OpenAPI builder logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/oas30-zGY2VGOJ.js | AI (source-diff): Content is standard minified Rollup/Vite bundle output for OpenAPI builder logic; no malicious patterns. Reject is for wrong-package reason, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/oas31-2ULMvMLl.js | AI (source-diff): Content is standard minified Rollup/Vite bundle output for OpenAPI builder logic; no malicious patterns. Reject is for wrong-package reason, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/oas31-Bx381qKf.js | AI (source-diff): Vite-bundled output for the oas31 module; same pattern as oas30 chunk. Content is readable minified OpenAPI builder code with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/oas30-E9r1WxRR.js | AI (source-diff): Vite-bundled output for the oas30 module; hash-suffixed filenames are standard Vite chunk naming. Content is readable minified OpenAPI builder code with no malicious patterns. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.5.0 | 1 / 16 | |
| 4.4.0 | 1 / 16 | |
| 4.3.3 | 1 / 14 | |
| 4.3.2 | 1 / 14 | |
| 4.3.1 | 1 / 14 | |
| 4.3.0 | 1 / 14 | |
| 4.2.2 | 1 / 14 | |
| 4.2.1 | 1 / 14 | |
| 4.1.1 | 1 / 14 | |
| 4.1.0 | 1 / 14 | |
| 4.0.4 | 1 / 14 | |
| 4.0.3 | 1 / 14 | |
| 4.0.2 | 1 / 14 | |
| 4.0.1 | 1 / 14 | |
| 4.0.0 | 1 / 14 | |
| 3.2.0 | 1 / 14 | |
| 3.1.2 | 1 / 14 | |
| 3.1.1 | 1 / 14 | |
| 3.1.0 | 1 / 14 | |
| 3.0.3 | 1 / 14 | |
| 3.0.2 | 1 / 13 | |
| 3.0.1 | 1 / 13 | |
| 3.0.0 | 1 / 13 |
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v4.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v4.2.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v4.2.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.