Installations
npm install 0-dd-trace-init-first-production
Releases
Unable to fetch releases
Developer
dave-inc
Developer Guide
Module System
CommonJS
Min. Node Version
Typescript Support
Yes
Node Version
10.17.0
NPM Version
6.13.7
Statistics
5 Commits
1 Watching
3 Branches
Updated on 01 Dec 2022
Languages
JavaScript (59.26%)
TypeScript (40.74%)
Total Downloads
Cumulative downloads
Total Downloads
44,972
Last day
100%
2
Compared to previous day
Last week
220%
32
Compared to previous week
Last month
-83.4%
90
Compared to previous month
Last year
33.3%
4,076
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
A package that initializes dd trace when the environment is production, (and is lexographically superior, so that it is sorted to be "first").
Usage
To use this package, import or require it.
import '0-dd-trace-init-first-production';
Naming
0-
- beginning with a-
is slightly prefered to me, but npmjs.com doesn't allow it. It just errors with a 404 if you try, so it might be a bug, but my gut says it's intentional. It's not consistent with the npm package though. Note that0-
is lexographically superior to00000-
.0-
is the most lexographically superior prefix for an npmjs.com package.dd-trace
- It's add-trace
lib at heart, so it's gotdd-trace
in it.init
- It runs theinit()
method.first
- This is kind of redundant with the0-
prefix, but this should remind developers that it belongs at the first, in case someone decides to name their package0--a
or something silly that is more superior. I admit that this solution isn't perfect, it's just more perfect than anything else I can think of.production
- It only runsinit()
if the node env is production. Someone might want a0-dd-trace-init-first
that runs always or something.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
branch protection is not maximal on development and all release branches
Details
- Info: 'allow deletion' disabled on branch 'master'
- Info: 'force pushes' disabled on branch 'master'
- Info: 'branch protection settings apply to administrators' is required to merge on branch 'master'
- Warn: required approving review count is 1 on branch 'master'
- Warn: codeowners review is required - but no codeowners file found in repo
- Warn: 'up-to-date branches' is disabled on branch 'master'
- Info: status check found to merge onto on branch 'master'
- Info: PRs are required in order to make changes on branch 'master'
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
project is archived
Details
- Warn: Repository is archived.
Reason
Found 0/5 approved changesets -- score normalized to 0
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
license file not detected
Details
- Warn: project does not have a license file
Score
3.3
/10
Last Scanned on 2024-11-25
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