Gathering detailed insights and metrics for lawl-spec-reporter
Gathering detailed insights and metrics for lawl-spec-reporter
🥀 Console spec reporter for Jasmine, with lulz. Forked from /bcaudan/jasmine-spec-reporter
Installations
npm install lawl-spec-reporterDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
0.12.2
NPM Version
2.8.4
Score
75.7
Supply Chain
81.9
Quality
74.8
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Languages
2
CoffeeScript
JavaScript
CoffeeScript (53.51%)
JavaScript (46.49%)
Developer
ItsASine
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
Apache-2.0 License
1 Stars
118 Commits
1 Watchers
1 Branches
4 Contributors
Updated on Aug 12, 2018
Maintainers
1
Package Meta Information
Latest Version
1.0.0
Package Id
lawl-spec-reporter@1.0.0
Size
168.51 kB
NPM Version
2.8.4
Node Version
0.12.2
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
Dependencies
1
Dev Dependencies
2
lawl-spec-reporter 
#OHAI
##Description
Spec reporter for jasmine, based on jasmine-spec-reporter, outputs in LolSpeak
Usage
Protractor
The lawl-spec-reporter can be used to enhance your Protractor tests execution report, utilizing the power of lulz.
###Customization
Have some project-specific words that you know could be lolified? Add them to the translation.json file!
##Credit
- LolSpeak translator, for the base translation file.
- jasmine-spec-reporter, for the vast majority of the base work
So, yeah, all I did was put it together and made it work :+1:
##Project Status
###1.0
Currently will take your suite and spec descriptions and convert them to lolspeak. Also outputs metrics to lolspeak.
###Future versions
- Make Stacktrace prettier (eww)
- Get the spec file working instead of just skipping the failures summary tests (note: the failures summary does print, see screenshot, but the test that's testing the tests is not working)
- Lolified failure summary
#KTHXBAI
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: Apache License 2.0: 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 'develop'
Score
3
/10
Last Scanned on 2025-07-07
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