
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
A `function(filename, specs)` thats checks if `'someFile.ext'` passes through an of Array of `minimatch` / `RegExp` / `callbacks` specs, with inclusion OR negation/exclusion '!' flag.
A function(filename, specs) thats checks if 'someFile.ext' passes through an of Array of minimatch / RegExp / callbacks specs, with inclusion OR negation/exclusion '!' flag
The Array of filename specifications (or simply filenames), can expressed in either:
String in gruntjs's-like expand minimatch format (eg '**/*.coffee') and its exclusion cousin (eg '!**/DRAFT*.*')
RegExps that matches filenames (eg /./) again with a
[..., '!', /regexp/, ...]
negation / exclusion pattern.
function(filename){} callback, returning true if filename is to be matched. Consistently it can have a negation / exclusion flag before it:[..., '!', function(f){ return f === 'excludeMe.js' }, ...]
```.
Note the trap: use a `true` (i.e matched) as the function result, preceded by '!' for **exclusion**. The common trap is to return a `false` for your *excluded matches* and then all your non-excluded with match with `true`, which is probably not what you want!.
* @todo: NOT IMPLEMENTED: An `Array<String|RegExp|Function|Array>, recursive, i.e
[ ..., ['AllowMe*.*', '!', function(f){ return f === 'excludeMe.js' }, [.., []], ...], ...]
# Examples
```javascript
var specs = [
'**/recources/*',
'!badFile.json',
/.*\.someExtension$/i, '!',
/.*\.excludeExtension$/i,
function(fn) { return fn === 'includedFile.ext' },
'!', function(fn) { return _.startsWith('DRAFT') }
];
isFileIn('someFile.someExtension', specs) // true
isFileIn('someFile.otherExtension', specs) // false
isFileIn('includedFile.ext', specs) //true
isFileIn('DRAFTFile.ext', specs) // false
See the specs for more examples.
The MIT License
Copyright (c) 2013-2014 Agelos Pikoulas (agelos.pikoulas@gmail.com)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
A `function(filename, specs)` thats checks if `'someFile.ext'` passes through an of Array of `minimatch` / `RegExp` / `callbacks` specs, with inclusion OR negation/exclusion '!' flag.
The npm package is_file_in receives a total of 8 weekly downloads. As such, is_file_in popularity was classified as not popular.
We found that is_file_in demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.