@kosdev-code/kos-freestyle-sdk
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:service-8u3gW6pr.cjs | AI (source-diff): Standard minified CJS bundle output for this SDK; readable domain logic, no exfiltration patterns. | ai | |
| source-diff | obfuscated-file:extension-utils-D3-Gwy8G.cjs | AI (source-diff): Standard minified CJS bundle output for this SDK; readable domain logic, no exfiltration patterns. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-Dx8XJMpl.cjs | AI (source-diff): Standard minified CJS bundle output; readable domain logic (carb-agitator, cartridge models), no exfiltration. | ai | |
| source-diff | obfuscated-file:extension-utils-yKcm_im8.cjs | AI (source-diff): Standard minified CJS bundle output; imports only sibling @kosdev-code packages, no malicious patterns. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-rmrOsUZq.cjs | AI (source-diff): Standard Vite/Rollup minified CJS bundle; content is normal SDK service code, not malicious. | ai | |
| source-diff | obfuscated-file:extension-utils-BUUtrM-T.cjs | AI (source-diff): Standard Vite/Rollup minified CJS bundle; content is normal SDK service code, not malicious. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-B1nEQ5f5.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output; readable business logic, no exfiltration or shell patterns. | ai | |
| source-diff | obfuscated-file:extension-utils-BkIqcOpm.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output; no malicious patterns, only internal SDK imports. | ai | |
| source-diff | obfuscated-file:extension-utils-BVDLwtKr.cjs | AI (source-diff): Standard minified build output for this SDK; pattern is consistent across versions. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-CDbljuRk.cjs | AI (source-diff): Standard minified build output for this SDK; pattern is consistent across versions. | ai | |
| source-diff | obfuscated-file:extension-utils-BY9yhVLb.cjs | AI (source-diff): Standard minified bundle output for this SDK; content is readable business logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-Dbdeo0JU.cjs | AI (source-diff): Standard minified bundle output for this SDK; content is readable business logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-BNSA2Xyl.cjs | AI (source-diff): Minified CJS bundle; readable domain logic (carb-agitator, cartridge models), no exfiltration or shell patterns. | ai | |
| source-diff | obfuscated-file:extension-utils-VVeh-q52.cjs | AI (source-diff): Minified CJS bundle from build toolchain; imports only sibling @kosdev-code/* packages, no malicious patterns. | ai | |
| source-diff | obfuscated-file:extension-utils-C8jLUyb0.cjs | AI (source-diff): Standard rollup/vite minified bundle; logic is readable, no exfiltration or shell patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped SDK with 171 versions; missing metadata is cosmetic, not indicative of spam. | ai | |
| source-diff | obfuscated-file:freestyle-registration-manager-CqOQC8rw.cjs | AI (source-diff): Standard rollup/vite minified bundle; imports only sibling @kosdev-code/* packages, no malicious patterns. | ai | |
| source-diff | obfuscated-file:extension-utils-DQSu9dSv.cjs | AI (source-diff): Build-tool minified CJS output (Vite/Rollup hash filenames). Code shows standard module re-exports of @kosdev-code deps. Stable pattern for this SDK. | ai | |
| source-diff | obfuscated-file:service-DSV9Dr2d.cjs | AI (source-diff): Build-tool minified CJS output with domain-specific beverage dispenser SDK logic. Standard bundled output, not malicious obfuscation. | ai |
Versions (showing 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 2 / 0 | |
| 3.0.3 | 2 / 0 | |
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.1.40 | 2 / 0 | |
| 2.1.39 | 2 / 0 | |
| 2.1.38 | 2 / 0 | |
| 2.1.37 | 2 / 0 | |
| 2.1.36 | 2 / 0 | |
| 2.1.35 | 2 / 0 | |
| 2.1.34 | 2 / 0 | |
| 2.1.33 | 2 / 0 | |
| 2.1.32 | 2 / 0 | |
| 2.1.31 | 2 / 0 | |
| 2.1.30 | 2 / 0 | |
| 2.1.29 | 2 / 0 | |
| 2.1.28 | 2 / 0 | |
| 2.1.27 | 2 / 0 | |
| 2.1.26 | 2 / 0 | |
| 2.1.25 | 2 / 0 | |
| 2.1.23 | 2 / 0 | |
| 2.1.22 | 2 / 0 | |
| 2.1.21 | 2 / 0 | |
| 2.1.20 | 2 / 0 | |
| 2.1.19 | 2 / 0 | |
| 2.1.18 | 2 / 0 | |
| 2.1.17 | 2 / 0 | |
| 2.1.16 | 2 / 0 | |
| 2.1.15 | 2 / 0 | |
| 2.1.14 | 2 / 0 | |
| 2.1.13 | 2 / 0 | |
| 2.1.12 | 2 / 0 | |
| 2.1.11 | 2 / 0 | |
| 2.1.10 | 2 / 0 | |
| 2.1.9 | 2 / 0 | |
| 2.1.8 | 2 / 0 | |
| 2.1.7 | 2 / 0 | |
| 2.1.6 | 2 / 0 | |
| 2.1.5 | 2 / 0 | |
| 2.1.4 | 2 / 0 | |
| 2.1.3 | 2 / 0 | |
| 2.1.2 | 2 / 0 | |
| 2.1.1 | 2 / 0 | |
| 2.1.0 | 2 / 0 | |
| 2.0.46 | 2 / 0 | |
| 2.0.45 | 2 / 0 | |
| 2.0.44 | 2 / 0 | |
| 2.0.43 | 2 / 0 | |
| 2.0.42 | 2 / 0 | |
| 2.0.41 | 2 / 0 |
v3.0.4
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.40
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.
v2.1.39
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.
v2.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.37
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.
v2.1.36
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.
v2.1.35
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.
v2.1.34
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.
v2.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.22
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.
v2.1.21
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.
v2.1.20
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.
v2.1.19
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.
v2.1.18
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.
v2.1.16
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.
v2.1.14
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.
v2.1.12
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.
v2.1.11
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.
v2.1.4
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.
v2.1.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.
v2.1.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.
v2.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
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.
v2.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
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.
v2.0.41
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.