node-opcua-chunkmanager MIT 43 versions

node-opcua-chunkmanager

npm Repository Homepage

pure nodejs OPCUA SDK - module chunkmanager

43

Versions

MIT

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

erossignon

Keywords

OPCUAopcuam2miotopc uainternet of things

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:chalk	AI (phantom-deps): Likely used in compiled dist output; well-known dep, no malicious pattern.	ai	2026/07/23
provenance	publisher-changed	AI (provenance): Transition from erossignon to GitHub Actions is a documented CI/CD migration, backed by SLSA provenance attestation.	ai	2026/05/19
publish-pattern	dormant-publish	AI (publish-pattern): Long-lived monorepo package; inactivity on this sub-package is normal; SLSA attestation confirms legitimate CI publish.	ai	2026/05/19
dependencies	unvetted-dep:node-opcua-factory	AI (dependencies): Sibling monorepo package from the same node-opcua org; stable pattern across all versions.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-packet-assembler	AI (dependencies): Sibling monorepo package from the same node-opcua org; stable pattern across all versions.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-basic-types	AI (dependencies): Sibling monorepo package from the same node-opcua org; stable pattern across all versions.	ai	2026/04/29
dependencies	unvetted-dep:node-opcua-binary-stream	AI (dependencies): Sibling monorepo package from the same node-opcua org; stable pattern across all versions.	ai	2026/04/29

Versions (showing 43 of 143)

Version	Deps	Published
2.37.0	7 / 4	2021-04-06
2.36.0	7 / 4	2021-03-06
2.35.0	7 / 4	2021-03-06
2.34.0	7 / 4	2021-03-02
2.32.0	7 / 4	2021-02-04
2.31.0	7 / 4	2021-01-23
2.29.0	7 / 4	2021-01-11
2.28.0	7 / 4	2020-11-30
2.27.1	7 / 4	2020-11-22
2.27.0	7 / 4	2020-11-21
2.22.0	7 / 4	2020-10-21
2.20.0	7 / 4	2020-10-11
2.19.0	7 / 4	2020-10-02
2.18.0	7 / 4	2020-09-28
2.17.0	7 / 4	2020-09-23
2.16.0	7 / 4	2020-09-18
2.13.0	8 / 5	2020-09-01
2.11.0	8 / 5	2020-08-19
2.10.0	8 / 5	2020-08-11
2.9.0	8 / 5	2020-08-07
2.8.1	8 / 5	2020-07-24
2.8.0	8 / 5	2020-07-21
2.7.0	8 / 5	2020-06-20
2.6.5	8 / 5	2020-06-12
2.6.1	8 / 5	2020-05-30
2.5.10	8 / 5	2020-05-06
2.5.9	8 / 5	2020-04-28
2.5.8	8 / 5	2020-04-20
2.5.6	8 / 5	2020-04-09
2.5.5	8 / 5	2020-04-08
2.5.2	8 / 5	2020-03-24
2.5.1	8 / 5	2020-03-20
2.4.2	8 / 5	2020-01-14
2.4.0	8 / 5	2019-11-24
2.3.0	8 / 5	2019-11-14
2.2.0	8 / 5	2019-10-27
2.1.6	8 / 5	2019-09-08
2.1.5	8 / 5	2019-08-17
2.1.3	8 / 5	2019-08-10
2.1.2	8 / 5	2019-07-31
2.1.1	8 / 5	2019-07-27
2.1.0	8 / 5	2019-07-11
2.0.0	8 / 5	2019-05-30

v2.37.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.

v2.36.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.

v2.35.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.

v2.34.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.

v2.32.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.

v2.31.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.

v2.29.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.

v2.28.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.

v2.27.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.

v2.27.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.

v2.22.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.

v2.20.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.

v2.19.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.

v2.18.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.

v2.17.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.

v2.16.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.

v2.13.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.

v2.11.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.

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

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

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

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

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

v2.6.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.

v2.6.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.

v2.5.10

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.

v2.5.9

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.

v2.5.8

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.

v2.5.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.

v2.5.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.

v2.5.2

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.

v2.5.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.

v2.4.2

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.

v2.4.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.

v2.3.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.

v2.2.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.

v2.1.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.

v2.1.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.

v2.1.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.

v2.1.2

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.

v2.1.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.

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

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