@stream-io/feeds-client See license in LICENSE 38 versions

@stream-io/feeds-client

npm

38

Versions

See license in LICENSE

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

tbarbuglitschellenbachvishtreestream-release-botvangalilea88zita.szuperacaleb.murphymartincupela

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	no-description	AI (npm-metadata): Scoped internal SDK package; missing description is a style issue, not a risk signal.	ai	2026/05/02
bogus-package	bogus-package	AI (bogus-package): Established Stream.io org SDK; sparse metadata is a style choice, not a spam/malware signal.	ai	2026/05/02
dependencies	unvetted-dep:@stream-io/filter	AI (dependencies): Internal @stream-io org dependency; consistent with the package's ecosystem.	ai	2026/05/02
dependencies	unvetted-dep:@stream-io/logger	AI (dependencies): Internal @stream-io org dependency; consistent with the package's ecosystem.	ai	2026/05/02
dependencies	unvetted-dep:@stream-io/state-store	AI (dependencies): Internal @stream-io org dependency; consistent with the package's ecosystem.	ai	2026/05/02

Versions (showing 38 of 38)

Version	Deps	Published
2.3.0	4 / 15	2026-05-27
2.2.0	4 / 15	2026-05-21
2.1.0	4 / 15	2026-05-20
2.0.0	4 / 15	2026-05-04
1.10.1	4 / 15	2026-04-29
1.10.0	4 / 15	2026-04-16
1.9.0	4 / 15	2026-04-07
1.8.0	4 / 15	2026-04-02
0.3.33	3 / 10	2026-01-08
0.3.32	3 / 10	2025-12-26
0.3.31	3 / 10	2025-12-26
0.3.30	3 / 10	2025-12-23
0.3.29	3 / 10	2025-12-22
0.3.28	3 / 10	2025-12-18
0.3.27	3 / 10	2025-12-17
0.3.26	3 / 11	2025-12-17
0.3.25	3 / 11	2025-12-17
0.3.24	3 / 11	2025-12-17
0.3.23	3 / 11	2025-12-16
0.3.22	3 / 11	2025-12-16
0.3.21	3 / 11	2025-12-16
0.3.20	3 / 11	2025-12-15
0.3.19	3 / 11	2025-12-11
0.3.18	3 / 11	2025-12-10
0.3.17	3 / 11	2025-12-08
0.3.16	3 / 11	2025-12-03
0.3.15	3 / 11	2025-11-28
0.3.14	3 / 11	2025-11-28
0.3.13	3 / 11	2025-11-19
0.3.12	3 / 11	2025-11-18
0.3.11	3 / 11	2025-11-17
0.3.10	3 / 11	2025-11-14
0.3.9	3 / 11	2025-11-14
0.3.8	3 / 11	2025-11-12
0.3.7	3 / 11	2025-11-11
0.3.6	3 / 11	2025-11-05
0.3.5	3 / 11	2025-11-04
0.3.4	3 / 11	2025-11-04

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

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.0

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.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.

v1.9.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.

v1.8.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.

v0.3.33

1 finding

LOW No provenance attestation provenance

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

v0.3.32

1 finding

LOW No provenance attestation provenance

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

v0.3.31

1 finding

LOW No provenance attestation provenance

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

v0.3.30

1 finding

LOW No provenance attestation provenance

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

v0.3.29

1 finding

LOW No provenance attestation provenance

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

v0.3.28

1 finding

LOW No provenance attestation provenance

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

v0.3.27

1 finding

LOW No provenance attestation provenance

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

v0.3.26

1 finding

LOW No provenance attestation provenance

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

v0.3.25

1 finding

LOW No provenance attestation provenance

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

v0.3.24

1 finding

LOW No provenance attestation provenance

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

v0.3.23

1 finding

LOW No provenance attestation provenance

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

v0.3.22

1 finding

LOW No provenance attestation provenance

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

v0.3.21

1 finding

LOW No provenance attestation provenance

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

v0.3.20

1 finding

LOW No provenance attestation provenance

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

v0.3.19

1 finding

LOW No provenance attestation provenance

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

v0.3.18

1 finding

LOW No provenance attestation provenance

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

v0.3.17

1 finding

LOW No provenance attestation provenance

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

v0.3.16

1 finding

LOW No provenance attestation provenance

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

v0.3.15

1 finding

LOW No provenance attestation provenance

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

v0.3.14

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

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.

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

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.

v0.3.5

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.

v0.3.4

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.