Gathering detailed insights and metrics for typeorm-postgres-naming-strategies
Gathering detailed insights and metrics for typeorm-postgres-naming-strategies
Custom naming strategies for typeorm
Installations
npm install typeorm-postgres-naming-strategiesDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Node Version
18.12.0
NPM Version
8.19.2
Releases
Unable to fetch releases
Languages
2
TypeScript
JavaScript
TypeScript (94.78%)
JavaScript (5.22%)
Developer
nopain2110
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
1 Stars
32 Commits
1 Branches
1 Contributors
Updated on Oct 03, 2022
Maintainers
1
Package Meta Information
Latest Version
3.0.2
Package Id
typeorm-postgres-naming-strategies@3.0.2
Unpacked Size
11.74 kB
Size
3.59 kB
File Count
17
NPM Version
8.19.2
Node Version
18.12.0
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Typeorm naming strategies
This package provides a few (one, at the moment) useful custom naming strategies. It alterates the name of columns, relations and other fields in database.
For example, using the snake strategy, if you have a model like this:
1class User { 2 @Column() 3 createdAt; 4}
In the DB the createdAt field will be created_at
Naming strategies available
- Snake
Installation
It's available as an npm package
1npm install typeorm-postgres-naming-strategies --save
Or using yarn
1yarn add typeorm-postgres-naming-strategies
Usage
1import { createConnection } from 'typeorm'; 2import { PostgresNamingStrategy } from 'typeorm-postgres-naming-strategies'; 3 4await createConnection({ 5 ... 6 namingStrategy: new PostgresNamingStrategy(), // Here you'r using the strategy! 7});
Alternatively you can use it in combination with a ormconfig.js
1// Use require instead of import 2const PostgresNamingStrategy = require("typeorm-postgres-naming-strategies").PostgresNamingStrategy 3 4module.exports = { 5 ... 6 namingStrategy: new PostgresNamingStrategy(), 7}
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
15 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-776f-qx25-q3cc
Score
1.7
/10
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More