skipper MIT 49 versions

skipper

npm Repository Homepage

Bodyparser for Express/Sails. Exposes simple API for streaming multiple files to disk, S3, etc. without buffering to a .tmp directory.

49

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

particlebananasgress454balderdashymikermcneileashaw

Keywords

bodyparseruploadsailsexpressconnectstreamingfile-uploadskipper

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): eashaw is a Balderdashy org member with 856 approved packages; publisher change reflects legitimate internal team transition within the Sails.js org.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): eashaw is a known Balderdashy contributor; maintainer addition is a legitimate org-internal handoff, not a hostile takeover.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): @sailshq/lodash is the official Sails.js org lodash fork, replacing plain lodash. This is a well-known safe pattern in the Sails ecosystem.	ai	2026/04/24

Versions (showing 49 of 49)

Version	Deps	Published
0.9.8	8 / 8	2026-05-27
0.9.7	9 / 8	2026-05-18
0.9.6	9 / 8	2026-02-09
0.9.5	9 / 8	2024-09-11
0.9.4	9 / 8	2023-07-21
0.9.3	9 / 8	2023-02-17
0.9.2	9 / 8	2022-08-11
0.9.1	9 / 8	2021-09-16
0.9.0	9 / 8	2021-08-03
0.8.7	11 / 7	2018-08-22
0.8.6	11 / 7	2018-08-22
0.8.5	11 / 7	2018-03-28
0.8.4	11 / 7	2017-11-04
0.8.3	11 / 7	2017-11-04
0.8.2	11 / 7	2017-03-06
0.8.1	11 / 7	2017-03-01
0.8.0	11 / 7	2017-01-25
0.7.6	11 / 8	2017-03-06
0.7.5	11 / 8	2017-03-02
0.7.4	11 / 8	2017-01-25
0.7.3	11 / 8	2016-12-08
0.7.2	11 / 8	2016-11-30
0.7.1	11 / 8	2016-11-16
0.7.0	11 / 8	2016-11-15
0.6.5	11 / 8	2016-11-15
0.6.4	11 / 8	2016-08-04
0.6.3	11 / 8	2016-08-02
0.6.2	11 / 8	2016-07-07
0.6.1	12 / 8	2016-06-21
0.6.0	12 / 8	2016-06-20
0.5.9	11 / 8	2016-01-06
0.5.8	11 / 8	2015-10-06
0.5.7	11 / 8	2015-09-18
0.5.5	11 / 8	2015-01-26
0.5.4	11 / 8	2015-01-23
0.5.3	11 / 8	2014-08-06
0.5.2	11 / 8	2014-08-04
0.5.1	11 / 8	2014-08-04
0.5.0	11 / 8	2014-08-04
0.4.0	11 / 8	2014-08-04
0.2.1	10 / 8	2014-07-30
0.1.8	10 / 8	2014-06-09
0.1.7	10 / 8	2014-06-09
0.1.6	10 / 8	2014-05-13
0.1.5	9 / 7	2014-05-11
0.1.3	9 / 7	2014-05-07
0.1.2	7 / 6	2014-04-07
0.1.1	7 / 5	2014-04-03
0.1.0	7 / 4	2014-02-22

v0.9.8

1 finding

LOW No provenance attestation provenance

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

v0.9.7

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.5

1 finding

LOW No provenance attestation provenance

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

v0.9.4

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

2 findings

HIGH Publisher changed: mikermcneil → eashaw (on 2021-09-16) provenance

This version was published by a different npm account than previous versions on 2021-09-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.7

1 finding

LOW No provenance attestation provenance

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

v0.8.6

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 2018-08-22) provenance

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

v0.8.5

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 2018-03-28) provenance

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

v0.8.4

1 finding

LOW No provenance attestation provenance

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

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.6

1 finding

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.9

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-01-06) provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

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: balderdashy → mikermcneil (on 2015-01-23) provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

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.