@beechcms/api
```txt npm install npm run dev ```
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:assets/dashboard/assets/index-CHxxc_id.js | AI (source-diff): Standard Vite-minified React bundle for CMS dashboard UI; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:assets/dashboard/assets/index-BMkd1Irh.js | AI (source-diff): Vite-bundled React dashboard frontend; minified JS is expected for this CMS package. | ai | |
| source-diff | obfuscated-file:assets/dashboard/assets/index-C1P9BXnU.js | AI (source-diff): Standard Vite/React minified dashboard bundle; sample shows recognizable React runtime, not malicious obfuscation. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @beechcms/api is a CMS API package, not a typosquat of hapi; Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package name; no relation to ajv. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package name; no relation to pg driver. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package name; no relation to joi. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 5 / 5 | |
| 0.4.3 | 5 / 5 | |
| 0.4.2 | 5 / 5 | |
| 0.4.1 | 5 / 5 | |
| 0.4.0 | 5 / 5 |
v0.5.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.
v0.4.3
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.
v0.4.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.
v0.4.1
2 findingsPackage name '@beechcms/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsPackage name '@beechcms/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.