← Home

sails.io.js-dist

npm Repository Homepage

Distribution version of sails.io.js for browsers, including bundled socket.io-client.

25
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mikermcneilsgress454

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): mikermcneil is the original Sailsjs founder and package author; the 2018 transition from sgress454 was a legitimate org handoff within balderdashy. Stable for this package. ai
email-domain unclaimed-email:mikermcneil AI (email-domain): The '@mikermcneil' in the author field is a Twitter handle placeholder, not a real email domain. Not an exploitable identity vector. ai
semgrep semgrep:new-function-constructor AI (semgrep): The new Function() usage is actually new ActiveXObject() obfuscated in a minified browser bundle — a legacy IE XHR shim, not dynamic code execution from untrusted input. ai

Versions (showing 25 of 25)

Version Deps Published
1.2.1 0 / 0
1.2.0 0 / 0
1.1.13 0 / 0
1.1.12 0 / 0
1.1.11 0 / 0
1.1.10 0 / 0
1.1.9 0 / 0
1.1.8 0 / 0
1.1.7 0 / 0
1.1.6 0 / 0
1.1.5 0 / 0
1.1.4 0 / 0
1.1.3 0 / 0
1.1.2 0 / 0
1.1.1 0 / 0
1.1.0 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0
0.14.0 0 / 0
0.13.8 0 / 0
0.13.7 0 / 0
0.13.6 0 / 0
0.13.5 0 / 0
0.13.4 0 / 0
0.13.3 0 / 0

v1.2.1

3 findings
HIGH Publisher changed: sgress454 → mikermcneil (on 2018-03-19) provenance

This version was published by a different npm account than previous versions on 2018-03-19. This could indicate a legitimate maintainer transition or an account compromise.

HIGH Unclaimed maintainer email domain: mikermcneil email-domain

Maintainer email '@mikermcneil' uses domain 'mikermcneil' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.13

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mikermcneil → sgress454 (on 2017-10-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-18. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.10

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mikermcneil → sgress454 (on 2017-04-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-06. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.8

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sgress454 → mikermcneil (on 2017-03-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mikermcneil → sgress454 (on 2016-12-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-12-09. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sgress454 → mikermcneil (on 2016-12-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-12-08. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.