@bemedev/core
The core library of @bemedev, providing essential functionalities and utilities for the Bemedev ecosystem.
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:lib/.codebase.cjs | AI (source-diff): File is structured JSON metadata (codebase analysis output from @bemedev/codebase), not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:lib/.codebase.js | AI (source-diff): File is structured JSON metadata (codebase analysis output from @bemedev/codebase), not obfuscated malicious code. | ai | |
| npm-metadata | url-dep:cli | AI (npm-metadata): Self-referential file: dep for testing the package's own CLI; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @bemedev/core is the core library of the bemedev ecosystem, not a typosquat of cors. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): chokidar is a declared runtime dep used in CLI/watch tooling; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@bemedev/sleep | AI (phantom-deps): Same-org dep; phantom-dep heuristic misfires for indirectly-imported utilities. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 7 / 31 | |
| 0.4.4 | 7 / 31 | |
| 0.4.3 | 7 / 31 | |
| 0.4.2 | 7 / 31 | |
| 0.4.0 | 7 / 31 | |
| 0.3.1 | 6 / 33 | |
| 0.3.0 | 6 / 33 | |
| 0.2.0 | 5 / 34 | |
| 0.1.8 | 6 / 28 | |
| 0.1.7 | 6 / 28 | |
| 0.1.6 | 6 / 28 | |
| 0.1.5 | 6 / 28 | |
| 0.1.2 | 6 / 29 | |
| 0.1.1 | 6 / 30 | |
| 0.1.0 | 6 / 30 |
v0.5.0
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.1.8
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsPackage name '@bemedev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.