Gathering detailed insights and metrics for @codelenny/spectacle-docs
Gathering detailed insights and metrics for @codelenny/spectacle-docs
Beautiful static documentation generator for OpenAPI/Swagger 2.0
Installations
npm install @codelenny/spectacle-docsDeveloper Guide
BETA
Typescript
No
Module System
N/A
Node Version
5.8.0
NPM Version
3.9.6
Releases
Unable to fetch releases
Languages
7
HTML
JavaScript
CSS
SCSS
Handlebars
Makefile
Dockerfile
HTML (37.09%)
JavaScript (21.09%)
CSS (20.99%)
SCSS (11.15%)
Handlebars (9.57%)
Makefile (0.06%)
Dockerfile (0.05%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
NOASSERTION License
1,277 Stars
298 Commits
333 Forks
17 Watchers
10 Branches
28 Contributors
Updated on Jun 22, 2025
Maintainers
1
Package Meta Information
Latest Version
0.2.1
Package Id
@codelenny/spectacle-docs@0.2.1
Size
428.24 kB
NPM Version
3.9.6
Node Version
5.8.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
Dependencies
21
Spectacle
The gentleman at REST
Spectacle generates beautiful static HTML5 documentation from OpenAPI/Swagger 2.0 API specifications.
The goal of Spectacle is help you "save time and look good" by providing an extensible platform for auto generating your REST API docs. The default layout is a three column single page, similar to those employed by Stripe and Intercom.
See a demo of Spectacle in action here: http://cheesestore.github.io
Fork Information
This is a fork of spectacle that adds the following:
- Updated
grunt-sasstov2.0.0, which in turn usesnode-sassv4.x, including the fix for sass/node-sass#1589.
Features
- OpenAPI/Swagger 2.0 support: Support for the latest OpenAPI/Swagger specification.
- Highly configurable: Easily configurable Handlebars templates and SCSS styles so you can add your own design and flavour without going bald. See Custom Builds
- Markdown support: Render markdown written in any of your API descriptions.
- Clean responsive design: Responsive HTML5 and CSS3 layout built with Foundation 6 that looks great on all devices and screen sizes.
- Embed into your existing website: An embedded option so that generate partial docs without a HTML
<body>for convenient integration into your existing website. - Live preview developer mode: Development mode that starts a local HTTP server with a file watcher and live reload so you can preview live changes in your browser as you update your spec.
Usage
Simply install Spectacle from npm like so:
1npm install -g spectacle-docs
Next pass your swagger.json document use the CLI to generate your documentation.
1spectacle -d your_swagger_api.json 2 3# Or use the cheese.json example to test it out 4# spectacle -d -l test/fixtures/cheese.png test/fixtures/cheese.json
Your generated documentation will be located in the public directory by default. You can either copy the generated HTML to your web server, or view your docs by pointing your browser to http://localhost:4400/.
Configuration Options
The basic CLI options are detailed below:
1$ spectacle -h 2 3 Usage: spectacle spactacle [options] <specfile> 4 5 Options: 6 7 -h, --help output usage information 8 -V, --version output the version number 9 -C, --disable-css omit CSS generation (default: false) 10 -J, --disable-js omit JavaScript generation (default: false) 11 -e, --embeddable omit the HTML <body/> and generate the documentation content only (default: false) 12 -d, --development-mode start HTTP server with the file watcher and live reload (default: false) 13 -s, --start-server start the HTTP server without any development features 14 -p, --port <dir> the port number for the HTTP server to listen on (default: 4400) 15 -t, --target-dir <dir> the target build directory (default: public) 16 -f, --target-file <file> the target build HTML file (default: index.html) 17 -a, --app-dir <dir> the application source directory (default: app) 18 -l, --logo-file <file> specify a custom logo file (default: null) 19 -c, --config-file <file> specify a custom configuration file (default: app/lib/config.js)
Most options are self explanatory, but the following options warrant some further explanation:
-
--development-mode
-d: This option starts a development server with a file watcher and live reload, and will automatically regenerate your docs when any of your spec or app files change. -
--start-server
-s: This option starts a production server without any development options enabled that serves the contents of your--target-dir. -
--embeddable
-e: This option lets you build a minimal version of the documentation without the HTML<body>tags, so you can embed Spectacle into your own website template. More info on custom builds here. -
--app-dir
-a: This option overrides the default directory which contains all the Handlebars templates, SCSS, and JavaScript source files. This option is useful for development because you can copy the contents ofappto a remote location or a separate repo for custom builds. -
--target-dir
-t: This option specifies where the generated documentation HTML files will be output.
Custom Builds
The best option for building your own custom functionality into Spectacle is to fork Spectacle on GitHub, and make your own modifications in source. This way you can keep up to date by merging changes from the master branch, and your can also contribute your updates back to master by creating a Pull Request if you think they improve Spectacle somehow.
To fork Spectacle go to https://github.com/sourcey/spectacle, and press the 'Fork' button. Now you can git clone git@github.com:<yourname>/spectacle.git to make your own changes.
Alternatively, you can just copy the contents of app from the main repo which contains all the source files such as templates, stylesheets and JavaScripts. Now just pass the path to your custom app path to the CLI like so: spectacle -a /path/to/your/app your_swagger_api.json
Optimizing Your Workflow
Using an API spec to generate your docs has a number of great advantages, such as:
- Maintain a single source: Save time by removing the need to maintain a separate API spec and API documentation.
- No more out-of-date documentation: Your documentation will always be up-to-date with your API spec.
- Be a better developer: Your entire API system will be more stable and robust when built around your spec as a single source of truth.
As developer we're always looking for ways to improve and optimize our workflow, and documentation is just the beginning. With a well written Swagger you can automate and generate many parts of your API system, such as:
- Inline Code Generators: Generate your Swagger JSON or YAML from your source code comments.
- Automate Testing: Automate testing for all your API endpoints.
- Code Generation: Automatically generate client and server code from your spec.
- Generate Documentation: Really?
For a list of open source Swagger based libraries in many languages check here: http://swagger.io/open-source-integrations/
More Information
More info is available on the Spectacle homepage.
Please use the GitHub issue tracker if you have any ideas or bugs to report.
All contributions are welcome.
Good luck and enjoy Spectacle!
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Reason
Found 6/8 approved changesets -- score normalized to 7
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- 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
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: containerImage not pinned by hash: Dockerfile:1: pin your Docker image by updating node:8-alpine to node:8-alpine@sha256:38f7bf07ffd72ac612ec8c829cb20ad416518dbb679768d7733c93175453f4d4
- Warn: npmCommand not pinned by hash: Dockerfile:11
- Info: 0 out of 1 containerImage dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 28 are checked with a SAST tool
Reason
48 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-fwr7-v2mv-hh25
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-h452-7996-h45h
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-4q6p-r6v2-jvc5
- Warn: Project is vulnerable to: GHSA-j383-35pm-c5h4
- Warn: Project is vulnerable to: GHSA-rm36-94g8-835r
- Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
- Warn: Project is vulnerable to: GHSA-jf85-cpcp-j695
- Warn: Project is vulnerable to: GHSA-fvqr-27wr-82fm
- Warn: Project is vulnerable to: GHSA-4xc9-xhrj-v574
- Warn: Project is vulnerable to: GHSA-x5rq-j2xg-h7qm
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-2m96-9w4j-wgv7
- Warn: Project is vulnerable to: GHSA-h726-x36v-rx45
- Warn: Project is vulnerable to: GHSA-5v2h-r2cx-5xgj
- Warn: Project is vulnerable to: GHSA-rrrm-qjm4-v8hf
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-hxm2-r34f-qmc5
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-qrpm-p2h7-hrv2
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-r8f7-9pfq-mjmv
- Warn: Project is vulnerable to: GHSA-rp65-9cf3-cjxr
- Warn: Project is vulnerable to: GHSA-566m-qj78-rww5
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-7mwh-4pqv-wmr8
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-76p7-773f-r4q5
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
- Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
- Warn: Project is vulnerable to: GHSA-3jfq-g458-7qm9
- Warn: Project is vulnerable to: GHSA-r628-mhmh-qjhw
- Warn: Project is vulnerable to: GHSA-9r2w-394v-53qc
- Warn: Project is vulnerable to: GHSA-5955-9wpr-37jh
- Warn: Project is vulnerable to: GHSA-qq89-hq3f-393p
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-v2p6-4mp7-3r9v
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Score
2.4
/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