@mdkva/tasbihkit
MDKVA TasbihKit provides clean, structured, and developer-friendly access to commonly used dhikr, tasbih counts, and remembrance phrases — ideal for spiritual apps, Islamic tools, and automation projects.
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/assets/day-and-night-CP9bzHc5.js | AI (source-diff): Long lines are Arabic Unicode text (Islamic dhikr data), not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/assets/general-OectKCHB.js | AI (source-diff): Long lines are Arabic Unicode text (Islamic dhikr data), not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/assets/magic-breaker-BO53SaFq.js | AI (source-diff): Long lines are Arabic Unicode text (Islamic dhikr data), not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/assets/post-prayer-DS3KYmFD.js | AI (source-diff): Long lines are Arabic Unicode text (Islamic dhikr data), not obfuscated code. | ai | |
| phantom-deps | phantom-dep:terser | AI (phantom-deps): Build-time minifier referenced in vite config; not a runtime import. | ai | |
| phantom-deps | phantom-dep:vite-plugin-css-injected-by-js | AI (phantom-deps): Vite build plugin; referenced in config, not runtime code. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 0 / 3 | |
| 1.3.3 | 2 / 1 | |
| 1.3.2 | 2 / 1 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.3 | 0 / 0 | |
| 1.2.2 | 0 / 0 | |
| 1.2.1 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.