← Home

@autofleet/outbreak

npm Repository Homepage

Spread yor headers between microserivces - have better context for http requests.

58
Versions
ISC
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

omergerybosmataaronlieblichnathanafdor_shaysephi-afroei-autofleetitayankridsalti12shaktipadaoleg.drushitsabir2matanl2208ofekrotemhilatd-autofleetariel-weissalexfadeeveladsaltiomrihaeli_autofleetmyarabsaar-enpitechbar_aftaltosianoasher-mentzerarmadosjaydatt-afor.autofleetalekshpitalnikaviranbeemiltayeb912andrew_autofleetkatrieltsepelevish-autofleetalonaf800elishalmanjordan12312danielautofleeteliranlevibenjaminmordukhovichdanielmarautofleetiftahsyoav_afmaxelementfjin_elementlei_elementachen_elementhemanth-raaj-gsaloni_autofleetgoni1992mqashoanitzanmadartomerymobrienwalker-elementomriluzongalinrebarshayaelransh12talcohenautofleetidan-levin-autofleetomrirothsaravanakumarputtaselvarajitaicohenafmakoto.afdor_bergnatanchechikrazr0saar_autofleetdavidi-autofleetlidorrosenyarden-rivkinordanadana_automeirizonshai-blaustiencravindraabhishek_001shrey-autofleetimmsaurabh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/index.cjs AI (source-diff): tsup bundle output for HTTP tracing lib, not true obfuscation. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are org teammates (autofleet emails), consistent with internal transfer. ai

Versions (showing 58 of 58)

Version Deps Published
2.6.24 0 / 10
2.6.23 0 / 10
2.6.22 0 / 10
2.6.21 0 / 10
2.6.20 0 / 10
2.6.19 0 / 10
2.6.15 0 / 10
2.6.14 0 / 10
2.6.13 0 / 10
2.6.12 0 / 10
2.6.8 0 / 10
2.6.7 0 / 10
2.6.6 0 / 10
2.6.5 0 / 10
2.6.4 0 / 10
2.6.3 0 / 10
2.6.2 0 / 10
2.5.4 0 / 10
2.5.3 0 / 10
2.5.2 0 / 10
2.5.1 0 / 10
2.5.0 0 / 10
2.4.32 0 / 10
2.4.31 0 / 10
2.4.30 0 / 10
2.4.28 0 / 10
2.4.27 0 / 10
2.4.26 0 / 10
2.4.25 0 / 10
2.4.24 0 / 9
2.4.23 0 / 10
2.4.22 0 / 10
2.4.21 0 / 10
2.4.20 0 / 10
2.4.19 0 / 10
2.4.18 0 / 10
2.4.17 0 / 10
2.4.16 0 / 10
2.4.15 0 / 10
2.4.14 0 / 10
2.4.12 0 / 10
2.4.11 0 / 10
2.4.10 0 / 10
2.4.9 0 / 10
2.4.8 0 / 10
2.4.7 0 / 10
2.4.6 0 / 10
2.4.5 0 / 10
2.4.4 0 / 10
2.4.3 0 / 10
2.4.2 0 / 10
2.4.1 0 / 10
2.4.0 0 / 17
2.3.2 0 / 17
2.3.1 0 / 17
2.3.0 0 / 17
2.1.0 0 / 16
2.0.1 0 / 16

v2.6.24

1 finding
LOW No provenance attestation provenance

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

v2.6.23

1 finding
LOW No provenance attestation provenance

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

v2.6.22

1 finding
LOW No provenance attestation provenance

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

v2.6.21

1 finding
LOW No provenance attestation provenance

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

v2.6.20

1 finding
LOW No provenance attestation provenance

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

v2.6.19

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.32

1 finding
LOW No provenance attestation provenance

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

v2.4.31

1 finding
LOW No provenance attestation provenance

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

v2.4.30

1 finding
LOW No provenance attestation provenance

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

v2.4.28

2 findings
MEDIUM Publisher changed: itayankri → GitHub Actions (on 2025-10-08, unremoved on npm for 282d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (itayankri) on 2025-10-08. It has since remained available on npm for 282 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.4.27

1 finding
LOW No provenance attestation provenance

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

v2.4.26

1 finding
LOW No provenance attestation provenance

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

v2.4.25

1 finding
LOW No provenance attestation provenance

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

v2.4.24

2 findings
MEDIUM Publisher changed: itayankri → GitHub Actions (on 2025-08-18, unremoved on npm for 333d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (itayankri) on 2025-08-18. It has since remained available on npm for 333 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.4.23

1 finding
LOW No provenance attestation provenance

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

v2.4.22

2 findings
MEDIUM Publisher changed: itayankri → GitHub Actions (on 2025-08-12, unremoved on npm for 339d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (itayankri) on 2025-08-12. It has since remained available on npm for 339 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.4.11

3 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Publisher changed: omergery → itayankri (on 2025-04-28, known maintainer) provenance

This version was published by a different npm account (itayankri) than the most recent previously approved version (omergery) on 2025-04-28, but itayankri is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.4.10

3 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Publisher changed: omergery → itayankri (on 2025-04-23, known maintainer) provenance

This version was published by a different npm account (itayankri) than the most recent previously approved version (omergery) on 2025-04-23, but itayankri is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.4.9

3 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Publisher changed: omergery → itayankri (on 2025-04-23, known maintainer) provenance

This version was published by a different npm account (itayankri) than the most recent previously approved version (omergery) on 2025-04-23, but itayankri is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.4.8

3 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Publisher changed: omergery → itayankri (on 2025-04-20, known maintainer) provenance

This version was published by a different npm account (itayankri) than the most recent previously approved version (omergery) on 2025-04-20, but itayankri is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.4.7

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.6

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.5

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.4

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.3

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.2

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.1

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.4.0

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.3.2

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.3.1

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.3.0

2 findings
HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

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.