Project

web-puc

0.01
Low commit activity in last 3 years
No release in over a year
web-pucfulldecent/web-pucHomepageDocumentationSource CodeBug TrackerWiki
Validate your web project uses the latest CSS & JS includes
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
33,078
Stars
6
Forks
2
Watchers
6
 Releases
Current version
0.4.4
Total releases
6
First release
2017-05-04
Latest release
2023-01-18
 Issues
Open Issues
0
Closed Issues
8
Total Issues
8
Issue Closure Rate
100%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
0
Merged Pull Requests
9
Pull Request Acceptance Rate
100%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2017-11-29
Reverse Dependencies
1

 Dependencies

Runtime

http
~> 5.1
rake
>= 12
 Project Readme

Web Package Update Checker Ruby

We find old Bootstrap, JQuery, etc. references in your web projects and tell you to update them.

Use web-puc in your unit testing or continuous integration testing to confirm that you are not using outdated packages. We support packages that are included via CDN as well as mix-ins and Javascript/CSS/Fonts that are subsetted or compiled into your own files! We support ANY web front-end including HTML, PHP, Ruby, ASP, Cold Fusion.

For a full example of using web-puc with Travis CI for integration testing, please see https://github.com/fulldecent/sourcespeak and its .travis.yml file.

Synopsis

web-puc [-e glob] [-s] [-u] target ...

The following options are available:

Option Short Description
--exclude GLOB -e GLOB Exclude from consideration all files matching GLOB
--allow-supported -s Allow supported versions even if not latest
--update -u Update web package database

Return status is zero for success and non-zero if errors are found.

Output format:

web-puc 0.4.1
hello.html:15:Old version Bootstrap v3.0.0 (http://getbootstrap.com)

Ruby

Or access this tool using the web-puc Ruby gem.

Project layout

  • web-puc - the main executable
  • packages/ - database of package information
  • package-spiders/ - tools for updating the packages/ directory
  • tests/ - unit tests

Package recognition

We recognize packages by three types of matching:

  • CDN: is an inclusion (like <script src="..."> or <link href="...">) to a file on a popular content distribution network. For example, when this was written, //netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css was an old version, but //netdna.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css was current

  • Identifier: is a string like Bootstrap v3.0.0 (http://getbootstrap.com) which would indicate a file in your project contains specific code (web-puc gleans information from your files' contents, not names)

  • Content Matcher: is a string like .form-control{position:relative;z-index:2;float:left; that would indicate, for example, that are using Twitter Bootstrap 3.1.1 even if you later minify and package all your CSS files together

Project roadmap

Please Star (or Watch!) this project for updates and to get involved. Following is a roadmap:

  • Create more package-updaters for all MaxCDN packages and JQuery
  • Store packages/ and package-spiders/ in a separate repository and have web-puc use git pull to update
  • Have web-put.sh warn if packages/ was updated too long ago (like Composer)
  • Advertise the availability of this project