@polyglot-bundles/ja-grammar-syllabi
Japanese grammar syllabi based on Tae Kim's Grammar Guide
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-12-quotations-DyfUF3PB.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-01-sentence-structure-CZx8m4jr.js | AI (source-diff): Vite-bundled MDX content as a long string literal; plaintext educational data, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/lesson-02-na-adjectives-DRTo3uJx.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-03-i-adjectives-DAJLwDH-.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-04-verbs-BjSk6q7z.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-05-te-form-Chjz_AHe.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-06-volitional-CwGODn4D.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-07-passive-causative-BCdvILrR.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-08-conditionals-Di7E-9KB.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-09-requests-ability-Bxn2CX8y.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-10-giving-receiving-Drt9DkWO.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-11-combined-forms-Cpt1h-OM.js | AI (source-diff): Same pattern: bundled MDX lesson content, no executable payload. | ai | |
| source-diff | obfuscated-file:dist/lesson-01-sentence-structure-DwlPCvDt.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-02-na-adjectives-CcpEaYGb.js | AI (source-diff): Same pattern: bundled MDX lesson content, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/lesson-03-i-adjectives-CvgN7-x9.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-04-verbs-DohacRUk.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-05-te-form-CrtNXzpY.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-06-volitional-BvJhr6j8.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-07-passive-causative-BHtKICJl.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-08-conditionals-n4KPvQya.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-09-requests-ability-BJLDVsEu.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-10-giving-receiving-DItHZUO1.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-11-combined-forms-BJM5NL1E.js | AI (source-diff): Bundled MDX lesson content. | ai | |
| source-diff | obfuscated-file:dist/lesson-12-quotations-DOmkQmhY.js | AI (source-diff): Bundled MDX lesson content. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 0 / 7 | |
| 0.1.10 | 0 / 7 | |
| 0.1.9 | 0 / 7 | |
| 0.1.8 | 0 / 7 | |
| 0.1.7 | 0 / 6 | |
| 0.1.6 | 0 / 6 | |
| 0.1.5 | 0 / 6 | |
| 0.1.4 | 1 / 5 | |
| 0.1.3 | 1 / 4 | |
| 0.1.2 | 1 / 4 |
v0.1.11
13 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.
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.
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.
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.
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.
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.1.10
13 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.
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.
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.
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.
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.
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.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
13 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.
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.
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.
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.
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.
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.1.5
13 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.
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.
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.
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.
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.
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.1.4
13 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.
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.
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.
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.
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.
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.1.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.