
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.
Composable message-based validation
$ npm install not-valid --save
import { validate } from "not-valid";
// Use createValidator to specify a rule and the message given for breaking that rule
const mustContainA = createValidator<string>(v => v.indexOf("A") !== -1, "Value must contain the letter 'a'");
// pass in array of validation functions and a value to validate
validate([ mustContainA ], "cheese"); // [ "Value must contain the letter 'a'" ] - returns error messages
// can use a factory pattern for your validation methods to make things nice
const mustContain = (requirement: any) => {
return createValidator<string | Array<any>>(v => v.indexOf(requirement) !== -1, `Value must contain '${requirement}'`);
};
const lengthWithinBounds = (min: number, max: number) => {
return createValidator<string>(v => v.length < min || v.length > max, `Value must have length between ${min} and ${max}`);
};
// you can pass in multiple validators
validate([
mustContain("Z"),
lengthWithinBounds(2, 6)
], "Too long a string, they say!"); // [ "Value must contain 'Z'", "Value must have length between 2 and 6" ]
A number of validation functions come bundled with this package. You can use them like so:
import { validators } from "not-valid";
validate([
validators.validLength({ min: 6, max: 12 })
], "Good value");
The validators included are as follows:
requiredStringrequiredNumbervalidLengthvalidEmailvalidAlphaNumericvalidOptionvalidPhoneNumbervalidNINumbervalidUKDrivingLicencevalidSortCodevalidBankAccountNumbervalidVATNumberA validation function must take in a value value, and return Result.Pass if value is valid, or Result.Fail(message) is value is invalid. They can also return Result.Stop, which will silently stop the validation cycle (no more errors).
This can be done with the helper method createValidator in not-valid:
import { createValidator } from "not-valid";
const mustContainA = createValidator<string>(v => v.indexOf("A") !== -1, "Value must contain the letter 'a'");
You can use factory patterns around this to make it nicer:
const mustContain = (requirement: any) => {
return createValidator<string | Array<any>>(v => v.indexOf(requirement) !== -1, `Value must contain '${requirement}'`);
};
All validators (except for validators that explicitly check for "required") should treat empty string, null and undefined as valid. This is because we can combine validators with "required" validators in order to enforce something being valid and not empty, but also allows us to accept nothing being entered if desired.
The third parameter of validate is an object containing options.
interface ValidationOptions {
sequential?: boolean;
}
sequentialDefault: true
The validation will break on the first error, therefore only returning a single validation error.
validate([ something, another ], 5, { sequential: false });
If something fails validation, another will not be called.
Made with :sparkling_heart: by NewOrbit in Oxfordshire, and licensed under the MIT Licence
FAQs
Composable message-based validation
The npm package not-valid receives a total of 628 weekly downloads. As such, not-valid popularity was classified as not popular.
We found that not-valid demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 6 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
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.