@ticatec/node-common-library
A comprehensive Node.js database access framework providing robust abstractions for database connection management, SQL execution, transaction handling, pagination, and dynamic query building.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long-tenured trusted publisher resuming maintenance, no behavioral red flags. | ai | |
| npm-metadata | url-dep:@ticatec/logger-wrapper | AI (npm-metadata): devDependency-only local file link for sibling package, not shipped. | ai | |
| dependencies | unvetted-dep:@ticatec/singleton-log4js | AI (dependencies): Same-author companion package within ticatec's own ecosystem, low risk. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 2 / 7 | |
| 2.4.0 | 1 / 3 | |
| 2.3.0 | 1 / 3 | |
| 2.2.2 | 1 / 3 | |
| 2.2.1 | 1 / 3 | |
| 2.2.0 | 1 / 3 | |
| 2.1.11 | 1 / 3 | |
| 2.1.9 | 1 / 1 | |
| 2.1.8 | 1 / 1 | |
| 2.1.7 | 1 / 1 | |
| 2.1.6 | 1 / 1 | |
| 2.1.5 | 1 / 1 | |
| 2.1.4 | 1 / 1 | |
| 2.1.3 | 1 / 1 | |
| 2.1.2 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.27 | 1 / 1 | |
| 2.0.26 | 1 / 1 | |
| 2.0.25 | 1 / 1 | |
| 2.0.24 | 1 / 3 | |
| 2.0.23 | 1 / 3 | |
| 2.0.22 | 1 / 3 | |
| 2.0.21 | 1 / 3 | |
| 2.0.20 | 1 / 3 | |
| 2.0.18 | 2 / 1 | |
| 2.0.17 | 2 / 1 | |
| 2.0.16 | 2 / 1 | |
| 2.0.15 | 1 / 2 | |
| 2.0.14 | 1 / 2 | |
| 2.0.13 | 1 / 2 | |
| 2.0.12 | 1 / 2 | |
| 2.0.11 | 1 / 2 | |
| 2.0.10 | 1 / 2 | |
| 2.0.9 | 1 / 2 | |
| 2.0.8 | 1 / 1 | |
| 2.0.7 | 1 / 1 | |
| 2.0.6 | 1 / 1 | |
| 2.0.5 | 1 / 1 | |
| 2.0.4 | 1 / 1 | |
| 2.0.3 | 1 / 1 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 |
v3.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: henry.feng.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.