Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@sap/di.code-validation.core
Advanced tools
code validation controller for DI. returning issues in code according to validators configured
npm install di.code-validation.core --save-dev
executeForProject(projectPath, workspaceRootName, configuration, callbackFunction)
basePath - full path for the validated folder location
options - an object to set additional options for execution and return values processing.
options.pathPrefix - validation issues paths are relative to the project path. _pathPrefix enable to set constant prefix to the returned path.
configuration - configuration of the validators to execute. object of type ValidationConfig
callbackFunction - callback of results. (TBD: add also failure for callback?)
ValidationConfig structure:
{
"validators" : {
"validator1" : {
"extensions" : ['.js', '.xsjs'],
"filters": {
"levels" :["error", "warning", "info"]
}
},
"validator2" : {
"extensions" : ['.new'],
"filters": {
"levels" :["error"]
}
}
....
}
}
result structure:
{
"validator_id" : {
"issues" : {
"relative_file_path" : [
{
"category" : "Possible Error",
"checker" : "validator checker name",
"column" : 1,
"line" : 14,
"message" : "some message",
"path" : "relative_file_path",
"ruleId" : "optional name of rule",
"severity" : "error"
}
....
]
}
....
}
}
Each validator should implement following API:
validateFiles(validationMetadata, fileResources)
validationMetadata - contains following methods:
getRootPath() - workspaceRootName
getLevels() - array of levels of issues to return
fileResources - array of files to validate (TBD: enable validation by extension of regular expression)
getPath() - returns the file full path
getText() - returns the text in the file
node di.code-validation.core\bin\run.js "project file location" "client workspace root path"
--c "configuration file location" - file with validation configuration. if not supplied defaults used.
Example for configuration file:
var configParam = {
"validators" : {
"di.code-validation.js" : {
"extensions" : [".js", ".xsjs"],
"filters": {
"levels" :["error", "warning", "info"]
}
}
}
};
module.exports = configParam;
--l "log file" - location of the outpul log file. default is the execution directory
validators: {
"di.code-validation.js": {
extensions: [".js", ".xsjs"]
},
"di.code-validation.xml": {
extensions: [ ".xml"]
}
}
FAQs
Code validation
We found that @sap/di.code-validation.core 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.