ts-essentials
All essential TypeScript types in one place
Supply chain provenance
Status for the latest visible version.
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/is-exact/index.js | AI (source-diff): Standard tsc compiler output with inline base64 source map. This is normal for TypeScript type library dist files, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): ts-essentials-bot is the project's established CI publishing bot (1388 days, 64 approved). Transition from krzkaczor is legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): beraliv and ts-essentials-bot are known contributors/bots for this project; legitimate team expansion. | ai | |
| source-diff | obfuscated-file:dist/literal-types/index.js | AI (source-diff): Standard tsc output with inline base64 source map; not obfuscation. Stable pattern for this types-only package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Types-only library with many individual type modules; per-module dist files are expected from tsc compilation. | ai | |
| source-diff | obfuscated-file:dist/deep-pick/index.js | AI (source-diff): Standard tsc output with inline sourcemap; type-only module compiles to empty JS + base64 sourcemap. Not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/deep-omit/index.js | AI (source-diff): Standard tsc output with inline sourcemap; type-only module compiles to empty JS + base64 sourcemap. Not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/camel-case/index.js | AI (source-diff): Standard tsc output with inline sourcemap; type-only module compiles to empty JS + base64 sourcemap. Not obfuscated. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 10.2.0 | 0 / 10 | |
| 10.1.1 | 0 / 12 | |
| 10.1.0 | 0 / 12 | |
| 10.0.4 | 0 / 13 | |
| 10.0.3 | 0 / 10 | |
| 10.0.2 | 0 / 9 | |
| 10.0.1 | 0 / 9 | |
| 10.0.0 | 0 / 7 | |
| 9.4.2 | 0 / 7 | |
| 9.4.1 | 0 / 7 | |
| 9.4.0 | 0 / 7 | |
| 9.3.2 | 0 / 7 | |
| 9.3.1 | 0 / 7 | |
| 9.3.0 | 0 / 7 | |
| 9.2.0 | 0 / 7 | |
| 9.1.2 | 0 / 7 | |
| 9.1.0 | 0 / 7 | |
| 9.0.0 | 0 / 7 | |
| 8.1.0 | 0 / 7 | |
| 8.0.0 | 0 / 7 | |
| 7.0.3 | 0 / 7 | |
| 7.0.2 | 0 / 6 | |
| 7.0.1 | 0 / 5 | |
| 7.0.0 | 0 / 5 | |
| 6.0.7 | 0 / 5 | |
| 6.0.6 | 0 / 5 | |
| 6.0.5 | 0 / 5 | |
| 6.0.4 | 0 / 5 | |
| 6.0.3 | 0 / 5 | |
| 6.0.2 | 0 / 5 | |
| 6.0.1 | 0 / 5 | |
| 6.0.0 | 0 / 5 | |
| 5.0.0 | 0 / 5 | |
| 4.0.0 | 0 / 5 | |
| 3.0.5 | 0 / 5 | |
| 3.0.4 | 0 / 5 | |
| 3.0.3 | 0 / 5 | |
| 3.0.2 | 0 / 5 | |
| 3.0.1 | 0 / 5 | |
| 3.0.0 | 0 / 5 | |
| 2.0.12 | 0 / 5 | |
| 2.0.11 | 0 / 5 | |
| 2.0.10 | 0 / 5 | |
| 2.0.9 | 0 / 5 | |
| 2.0.8 | 0 / 5 | |
| 2.0.7 | 0 / 5 | |
| 2.0.6 | 0 / 5 | |
| 2.0.5 | 0 / 5 | |
| 2.0.4 | 0 / 5 | |
| 2.0.3 | 0 / 3 | |
| 2.0.2 | 0 / 3 | |
| 2.0.1 | 0 / 3 | |
| 2.0.0 | 0 / 3 | |
| 1.0.4 | 0 / 3 | |
| 1.0.3 | 0 / 2 | |
| 1.0.2 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.4 | 0 / 1 | |
| 0.0.3 | 0 / 1 | |
| 0.0.2 | 0 / 1 |
v10.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-26. This could indicate a legitimate maintainer transition or an account compromise.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
4 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.
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.
v9.4.1
4 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.
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.
v9.4.0
4 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.
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.
v9.3.2
4 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.
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.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
3 findingsThis version was published by a different npm account than previous versions on 2022-08-23. This could indicate a legitimate maintainer transition or an account compromise.
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.
v9.2.0
3 findingsThis version was published by a different npm account than previous versions on 2022-07-06. This could indicate a legitimate maintainer transition or an account compromise.
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.
v9.1.2
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.
v9.1.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.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.