
Research
/Security News
jscrambler npm Package Compromised in Supply Chain Attack
A compromised jscrambler npm release added a malicious preinstall hook that runs hidden native binaries on Linux, macOS, and Windows.
nativemodels
Advanced tools
Native Models provides a way to map objects in a clean and typed way. The main goal is to ensure runtime type checking and consistent models for APIs.
const { createModel } = require('nativemodels');
const { array, boolean, computed, date, int, object, string } = require('nativemodels/datatypes');
const photoSchema = {
ext: string(),
url: string().required(),
};
const contactSchema = {
email: string(),
phone: string(),
url: string(),
};
const userSchema = {
accountID: int().nullable(),
contact: object(contactSchema),
created: date(),
firstName: string().required(),
fullName: computed((record) => `${record.firstName} ${record.lastName}`),
isAdmin: boolean().nullable(),
lastName: string().required(),
photos: array(object(photoSchema)),
typeID: int().default(2),
};
const userModel = createModel(userSchema);
const johnSmith = userModel({
contact: {
email: 'j.smith@example.com',
},
firstName: 'John',
lastName: 'Smith',
photos: [
{
ext: '.jpg',
url: 'https://example.com/img.jpg',
},
],
});
// => { firstName: 'John', lastName: 'Smith', fullName: 'John Smith', ...}
const userRecords = [
{
firstName: 'John',
lastName: 'Smith',
},
{
firstName: 'Jane',
lastName: 'Doe',
},
];
const users = userRecords.map(userModel);
// => [{ firstName: 'John', lastName: 'Smith', fullName: 'John Smith', ...}]
const janeDoe = userModel({
...johnSmith,
firstName: 'Jane',
lastName: 'Doe',
});
// => { firstName: 'Jane', lastName: 'Doe', fullName: 'Jane Doe', ...}
Datatype methods that can be chained when defining schema.
Sets a default value if no value is set
Allows the value set to be null (useful for database models)
Forces the value to be required. Is ignored if default value is set
Requires the value that is passed in to be the correct datatype instead of coerced
If value is valid, returns true, else throws error. Name is key on object;
Parses the value being set. Used to extend base datatype
Custom types are types that are useful to have and common enough for use to include them in our library. They currently include
const { email, enumberable, guid, phone, url } = require('nativemodels/customtypes');
const model = createModel({
email: email(),
enumberable: enumberable(['FOO', 'BAR']),
guid: guid(),
phone: phone(),
url: url(),
});
Sometimes computed values aren't syncronous. To help you deal with that, we have provided the resolver method which will allow you to resolve all computed functions that are promises or async functions.
NOTE: You must return an async function, Promise or syncronous result. Generators will not work with this
WARNING: This is an N+1 unoptimized resolver meaning that for each nested array / object will require an extra iteration.
const { createModel, resolver } = require('nativemodels');
const { boolean, computed } = require('nativemodels/datatypes');
const schema = {
async: computed(
(record) =>
new Promise((succeed, reject) => (record.succeed ? succeed(1) : reject(new Error('Failed to resolve')))),
),
succeed: boolean().default(false),
};
const model = createModel(schema);
const data = model({ succeed: true });
const resolvedData = await resolver(data);
// => { async: 1, succeed: true }
You can provide a second option to resolver() that will allow you to receive back an object that has had the schema applied to it.
const { createModel, resolver } = require('nativemodels');
const { boolean, computed, int } = require('nativemodels/datatypes');
const schema = {
async: computed(
(record) =>
new Promise((succeed, reject) => (record.succeed ? succeed(1) : reject(new Error('Failed to resolve')))),
),
succeed: boolean().default(false),
};
const resolvedSchema = {
async: int(),
succeed: boolean(),
};
const model = createModel(schema);
const data = model({ succeed: true });
const resolvedData = await resolver(data, resolvedSchema);
// => { async: 1, succeed: true }
The caseSensitive option default(true) allows you to turn off caseSensitive matching. This is useful for ignoring and parsing user submitted data into a nice clean format while still maintaining model integrity
const { createModel } = require('nativemodels');
const { string } = require('nativemodels/datatypes');
const options = {
caseSensitive: false,
};
const schema = {
foo: string(),
};
const model = createModel(schema, options);
const data = model({ FOO: 'bar' });
// => { foo: 'bar' }
Options are shallow by default, so if you have a deeply nested object, you will need to pass down options by hand.
const { createModel } = require('nativemodels');
const { object, string } = require('nativemodels/datatypes');
const options = {
caseSensitive: false,
};
const schema = {
foo: string(),
};
const deepSchema = {
nested: object(schema, options),
};
const model = createModel(deepSchema, options);
const data = model({ Nested: { FOO: 'bar' } });
// => { nested: { foo: 'bar' } }
The strict option default(false) allows you to throw an error is the inital object you are assigning has extra keys. This is useful for validating data structure when coming from an unknown source
const { createModel } = require('nativemodels');
const { string } = require('nativemodels/datatypes');
const options = {
strict: true,
};
const schema = {
foo: string(),
};
const model = createModel(schema, options);
const data = model({ faa: 'bar' });
// => throw new Error(`Property: 'faa' is not defined in the schema`);
Options are shallow by default, so if you have a deeply nested object, you will need to pass down options by hand.
const { createModel } = require('nativemodels');
const { object, string } = require('nativemodels/datatypes');
const options = {
strict: true,
};
const schema = {
foo: string(),
};
const deepSchema = {
nested: object(schema, options),
};
const model = createModel(deepSchema, options);
const data = model({ nested: { faa: 'bar' } });
// => throw new Error(`Property: 'faa' is not defined in the schema`);
FAQs
Native Models for Javascript
The npm package nativemodels receives a total of 27 weekly downloads. As such, nativemodels popularity was classified as not popular.
We found that nativemodels 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
A compromised jscrambler npm release added a malicious preinstall hook that runs hidden native binaries on Linux, macOS, and Windows.

Research
/Security News
A malicious .NET package is typosquatting the Braintree SDK to steal live payment card data, merchant API keys, and host secrets from production apps.

Security News
/Research
Compromised Injective SDK npm version 1.20.21 exfiltrates wallet private keys and mnemonics through fake telemetry functionality.