
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
There are three ways you can run the monitor.
This form watches one path, and enters the run loop automatically. The first parameter is the path to watch, and the second parameter is an optional glob pattern or array of glob patterns that a file must match in order to trigger a callback. The default glob, if ommitted, is '**/*'
.
FSSM.monitor('/some/directory/', '**/*') do
update {|base, relative|}
delete {|base, relative|}
create {|base, relative|}
end
This form watches one or more paths, and enters the run loop automatically. The glob configuration call can be ommitted, and defaults to '**/*'
.
FSSM.monitor do
path '/some/directory/' do
glob '**/*.yml'
update {|base, relative|}
delete {|base, relative|}
create {|base, relative|}
end
path '/some/other/directory/' do
update {|base, relative|}
delete {|base, relative|}
create {|base, relative|}
end
end
This form doesn't enter the run loop automatically.
monitor = FSSM::Monitor.new
monitor.path '/some/directory/' do
update {|base, relative|}
delete {|base, relative|}
create {|base, relative|}
end
monitor.run
By default, FSSM monitors changes in files only. To enable monitoring of files and directories, pass option directories => true
in a hash to the monitor. Please note that this may not work as expected in all backends. For example:
FSSM::Monitor.new(:directories => true)
FSSM.monitor(dir, file_glob, :directories => true)
When directories are monitored, there's an additional third argument to the callbacks. Instead of
FSSM.monitor('/some/directory/', '**/*') do
update {|base, relative|}
delete {|base, relative|}
create {|base, relative|}
end
you get this:
FSSM.monitor('/some/directory/', '**/*', :directories => true) do
update {|base, relative, type|}
delete {|base, relative, type|}
create {|base, relative, type|}
end
The value of type
argument is either :file
or :directory
.
FAQs
Unknown package
We found that fssm demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers 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
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.