@bejibun/core MIT 58 versions

@bejibun/core

npm Repository Homepage

Core of Bejibun Framework

58

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

crenata

Keywords

bunbun frameworkcorebejibuntypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:pg	AI (phantom-deps): pg is a DB driver referenced in config/knex setup, not directly imported in source — stable false positive for this ORM-based framework.	ai	2026/05/28
phantom-deps	phantom-dep:csstype	AI (phantom-deps): Declared dependency; used in type definitions and build config.	ai	2026/05/18
phantom-deps	phantom-dep:bun-types	AI (phantom-deps): Declared dependency; used in type definitions and build config.	ai	2026/05/18
phantom-deps	phantom-dep:typescript	AI (phantom-deps): Declared dependency; used in build script and peer dependency.	ai	2026/05/18
phantom-deps	phantom-dep:undici-types	AI (phantom-deps): Declared dependency; used in type definitions and build config.	ai	2026/05/18
typosquat	typosquat.levenshtein:cors	AI (typosquat): @bejibun/core is the core of the Bejibun Framework, not a typosquat of cors; name similarity is coincidental.	ai	2026/04/29
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is used in RouterBuilder to load user-defined controller classes by path — standard framework plugin/routing pattern.	ai	2026/04/29

Versions (showing 58 of 58)

Version	Deps	Published
0.4.24	12 / 5	2026-06-03
0.4.23	12 / 5	2026-06-02
0.4.22	12 / 5	2026-06-01
0.4.21	12 / 5	2026-06-01
0.4.2	12 / 5	2026-05-31
0.4.1	12 / 5	2026-05-28
0.4.0	12 / 5	2026-05-28
0.3.16	12 / 5	2026-05-25
0.3.15	12 / 5	2026-05-21
0.3.14	12 / 5	2026-05-19
0.3.13	12 / 5	2026-05-12
0.3.12	12 / 5	2026-04-27
0.3.11	12 / 5	2026-04-27
0.3.1	12 / 5	2026-04-27
0.3.0	12 / 5	2026-04-22
0.2.18	12 / 5	2026-04-22
0.2.17	11 / 5	2026-04-15
0.2.16	10 / 4	2026-03-18
0.2.15	10 / 4	2026-03-02
0.2.14	10 / 4	2026-02-27
0.2.13	10 / 4	2026-02-24
0.2.12	10 / 4	2026-02-22
0.2.11	10 / 4	2026-02-13
0.2.1	10 / 4	2026-02-13
0.2.0	10 / 4	2026-02-12
0.1.73	10 / 4	2026-02-02
0.1.72	10 / 4	2026-01-29
0.1.71	10 / 4	2026-01-29
0.1.70	10 / 4	2026-01-19
0.1.69	10 / 4	2026-01-13
0.1.68	10 / 4	2026-01-02
0.1.67	10 / 4	2026-01-02
0.1.66	10 / 4	2025-12-31
0.1.65	10 / 4	2025-12-29
0.1.64	10 / 4	2025-12-25
0.1.63	10 / 4	2025-12-15
0.1.62	10 / 4	2025-12-15
0.1.61	10 / 4	2025-12-12
0.1.60	10 / 4	2025-12-10
0.1.59	10 / 4	2025-12-09
0.1.58	10 / 4	2025-12-09
0.1.57	10 / 4	2025-12-05
0.1.56	10 / 4	2025-12-03
0.1.55	10 / 4	2025-11-29
0.1.54	10 / 4	2025-11-28
0.1.53	10 / 4	2025-11-24
0.1.52	9 / 4	2025-11-16
0.1.51	9 / 3	2025-11-04
0.1.50	9 / 3	2025-11-02
0.1.29	6 / 3	2025-10-15
0.1.28	6 / 3	2025-10-15
0.1.23	6 / 4	2025-10-13
0.1.21	0 / 3	2025-10-12
0.1.20	0 / 3	2025-10-12
0.1.19	0 / 3	2025-10-12
0.1.18	0 / 3	2025-10-12
0.1.17	4 / 1	2025-10-12
0.1.16	4 / 1	2025-10-12

v0.4.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.73

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.72

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.71

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.70

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.69

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.67

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.66

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.64

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.63

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.62

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.61

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.60

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.59

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.58

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.57

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.56

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.54

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.53

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.52

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.51

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.