@polyglot-bundles/ko-syllabi
Korean syllabi - Hangul, Essentials, Numbers
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/lesson-03-DbPKUSuz.js | AI (source-diff): Vite-bundled MDX content as string literal; long lines are lesson text, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lesson-07-BSIN46hU.js | AI (source-diff): Same pattern: inlined MDX lesson content, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/lesson-08-BiIrzQsR.js | AI (source-diff): Same pattern: inlined MDX lesson content, not obfuscated code. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.5.2 | 0 / 6 | |
| 0.4.0 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.10 | 0 / 5 | |
| 0.2.9 | 0 / 5 | |
| 0.2.8 | 0 / 5 | |
| 0.1.2 | 0 / 5 | |
| 0.1.1 | 0 / 5 |
v0.5.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.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.