@ticatec/common-express-server

Enterprise-grade TypeScript framework for Express.js with built-in multi-tenant support, CRUD controllers, validation, authentication, and API gateway integration. Simplifies building scalable REST APIs with boilerplate-free routing, automatic error handl

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

henry.fengwangzh2024

Keywords

expresstypescriptnodejsrest-apiapicrudmiddlewarecontrollerbase-controllerroutingroutermulti-tenantmultitenancysaasauthenticationauthorizationvalidationerror-handlinglogginglog4jsexpress-frameworkapi-gatewayjwtrestserverframeworkboilerplatescaffoldingadmin-paneladmin-controllertenantimpersonationtypescript-expressexpress-middlewareapi-serverweb-frameworkbackendfullstackticateccommon-expressexpress-utilitiesrestful

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@ticatec/bean-validator	AI (dependencies): Same publisher org (@ticatec); stable internal dependency across versions.	ai	2026/05/22
phantom-deps	phantom-dep:@ticatec/node-common-library	AI (phantom-deps): Same-org runtime dep; phantom-dep heuristic likely fires because it's re-exported rather than directly imported.	ai	2026/05/09
provenance	no-provenance	AI (provenance): No provenance is common; no other risk signals present to elevate this.	ai	2026/05/09

Versions (showing 35 of 35)

Version	Deps	Published
0.5.7	0 / 7	2026-06-03
0.5.5	0 / 7	2026-05-26
0.5.4	0 / 7	2026-05-21
0.5.3	0 / 7	2026-05-21
0.5.2	0 / 7	2026-04-28
0.5.1	0 / 7	2026-04-26
0.5.0	0 / 7	2026-04-25
0.4.9	0 / 7	2026-04-25
0.4.7	0 / 7	2026-04-25
0.4.6	0 / 7	2026-04-25
0.4.5	0 / 7	2026-04-23
0.4.4	0 / 7	2026-04-23
0.4.3	0 / 7	2026-04-23
0.4.2	0 / 7	2026-04-23
0.4.1	0 / 7	2026-04-23
0.4.0	0 / 7	2026-04-23
0.3.2	0 / 7	2026-04-11
0.3.1	0 / 7	2026-03-21
0.3.0	0 / 7	2026-03-21
0.2.1	0 / 7	2026-03-21
0.2.0	0 / 7	2026-03-21
0.1.8	0 / 7	2026-02-09
0.1.7	0 / 7	2026-02-02
0.1.6	0 / 7	2026-01-20
0.1.5	0 / 7	2026-01-14
0.1.4	0 / 7	2026-01-12
0.1.3	0 / 7	2025-08-10
0.1.2	4 / 3	2025-08-07
0.0.8	3 / 2	2025-05-13
0.0.7	3 / 2	2025-05-13
0.0.6	3 / 2	2025-05-13
0.0.5	3 / 2	2025-05-10
0.0.4	3 / 2	2025-05-10
0.0.3	3 / 2	2025-05-10
0.0.1	3 / 4	2025-05-09

v0.5.7

1 finding

INFO No provenance attestation provenance

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

v0.5.5

1 finding

INFO No provenance attestation provenance

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

v0.5.4

1 finding

INFO No provenance attestation provenance

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

v0.5.3

1 finding

INFO No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

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.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

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.3.2

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.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

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.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

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.4

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.3

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.2

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.0.8

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.0.7

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.0.6

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.0.5

1 finding

INFO No provenance attestation provenance

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

v0.0.4

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.0.3

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.0.1

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.