Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
LinearWorkFlow
is a basic state machine for managing state change through a
single linear set of states. That is, there is only one valid sequence of states
and the work flow is either forward or backward through those steps.
Add this line to your application's Gemfile:
gem 'linear_work_flow'
And then execute:
$ bundle
Or install it yourself as:
$ gem install linear_work_flow
To create a new linear work flow, create a new class that inherits from
LinearWorkFlow::WorkFlow
with a class method states
that defines the series
of steps as an array, in the order the states are to be traversed.
class WorkFlow < LinearWorkFlow::WorkFlow
def self.states
[:one, :two, :three, :four]
end
end
A new instance of WorkFlow
will be created via new
and will have its state
set as the first state as defined in WorkFlow.states
.
work_flow = WorkFlow.new
work_flow.state == :one
Use the methods forward!
and back!
to change state.
work_flow.forward!
work_flow.state == :two
work_flow.forward!
work_flow.state == :three
work_flow.back!
work_flow.state == :two
first?
and last?
methods can be used to check if the work flow is at the beginning or
end of the defined states.
work_flow = WorkFlow.new
work_flow.first? == true
work_flow.last? == false
At any intermediate state the state can go back, go forward, or remain the same.
The permissible_states
method returns the states that match these actions.
If the state is at the first state there cannot be a back transition, so in
this case permissible_states
returns the current state and the go forward state.
Similarly, as the state cannot go forward from the last state, permissible_states
returns the go back state and the current state when the last state is the
current state.
work_flow = WorkFlow.new
work_flow.state == :one
work_flow.permissible_states == [:one, :two]
work_flow.forward!
work_flow.state == :two
work_flow.permissible_states == [:one, :two, :three]
work_flow.forward!
work_flow.state == :three
work_flow.permissible_states == [:two, :three, :four]
work_flow.forward!
work_flow.state == :four
work_flow.permissible_states == [:three, :four]
A work flow can be initiate at a particular state.
last_state = WorkFlow.states.last
work_flow = WorkFlow.at last_state
work_flow.state == last_state == :four
work_flow.last? == true
Use the can?
method to check whether a work flow can be move forward or back.
work_flow = WorkFlow.new
work_flow.can?(:back) == false
work_flow.can?(:forward) == true
work_flow.forward!
work_flow.can?(:back) == true
FAQs
Unknown package
We found that linear_work_flow 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.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.