cids MIT 44 versions

cids

npm Repository Homepage

CID Implementation in JavaScript

44

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

vmxdaviddiasdignifiedquireachingbrainrvagg

Keywords

multihashcidipld

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	source-size-tripled	AI (source-diff): Size increase is entirely explained by addition of webpack dist bundles (browser build artifacts via aegir). The main entry point src/index.js is unchanged.	ai	2026/04/24
source-diff	net-exec-file:dist/index.js	AI (source-diff): dist/index.js is a standard webpack browser bundle produced by aegir build. The 'network + code execution' pattern is webpack's module loader boilerplate, not malicious dropper behavior. Stable for this package.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): class-is is a well-known, legitimate IPFS/IPLD ecosystem utility for type-checking. No malicious signals.	ai	2026/04/24
semgrep	semgrep:hex-decode	AI (semgrep): Hardcoded literal hex byte '01' used as CID version prefix in encoding logic. Not payload obfuscation; stable false positive for this package.	ai	2026/04/24
typosquat	typosquat.levenshtein:cors	AI (typosquat): 'cids' is a legitimate IPFS Content Identifier package with no relation to 'cors'; the Levenshtein match is a false positive that will generalize across all versions.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): achingbrain is a long-standing contributor to this package and the broader IPFS/multiformats ecosystem with 782 approved packages; transition from vmx is a legitimate org handoff.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): achingbrain and rvagg are both listed contributors in package.json and known Protocol Labs/multiformats ecosystem maintainers; addition is a legitimate org-level change.	ai	2026/04/24

Versions (showing 44 of 44)

Version	Deps	Published
1.1.9	4 / 3	2021-09-02
1.1.8	4 / 3	2021-08-24
1.1.7	4 / 3	2021-06-15
1.1.6	4 / 3	2021-03-02
1.1.5	4 / 3	2021-01-13
1.1.4	4 / 3	2020-12-12
1.1.3	4 / 3	2020-12-11
1.1.2	4 / 3	2020-12-11
1.1.1	4 / 3	2020-12-11
1.1.0	4 / 2	2020-12-11
1.0.2	5 / 2	2020-10-14
1.0.1	5 / 2	2020-09-25
1.0.0	5 / 2	2020-08-04
0.8.3	5 / 4	2020-06-19
0.8.2	5 / 5	2020-06-15
0.8.1	5 / 5	2020-05-22
0.8.0	5 / 5	2020-03-24
0.7.5	5 / 5	2020-03-24
0.7.4	5 / 5	2020-03-16
0.7.3	4 / 5	2020-01-24
0.7.2	4 / 5	2020-01-14
0.7.1	4 / 5	2019-05-14
0.7.0	4 / 5	2019-05-09
0.6.0	4 / 5	2019-04-08
0.5.8	4 / 5	2019-03-14
0.5.7	4 / 5	2018-12-06
0.5.6	4 / 6	2018-11-22
0.5.5	4 / 6	2018-09-25
0.5.4	4 / 6	2018-09-24
0.5.3	3 / 6	2018-03-12
0.5.2	3 / 5	2017-10-06
0.5.1	3 / 5	2017-07-10
0.5.0	3 / 5	2017-03-30
0.4.2	3 / 4	2017-03-16
0.4.1	3 / 4	2017-02-09
0.4.0	3 / 4	2017-01-25
0.3.6	3 / 4	2017-01-21
0.3.5	3 / 4	2016-12-16
0.3.4	3 / 4	2016-12-08
0.3.3	3 / 4	2016-12-07
0.3.2	3 / 4	2016-12-07
0.3.0	3 / 4	2016-12-05
0.2.0	3 / 4	2016-10-24
0.1.1	2 / 4	2016-09-09

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

HIGH Publisher changed: vmx → achingbrain (on 2021-08-24) provenance

This version was published by a different npm account than previous versions on 2021-08-24. 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.

v1.1.7

2 findings

HIGH Publisher changed: vmx → achingbrain (on 2021-06-15) provenance

This version was published by a different npm account than previous versions on 2021-06-15. 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.

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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

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

2 findings

HIGH New file with network + code execution: dist/index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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: daviddias → vmx (on 2018-09-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-24. 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

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: dignifiedquire → daviddias (on 2017-07-10) provenance

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

v0.5.0

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: daviddias → dignifiedquire (on 2017-03-30) provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

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

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

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: dignifiedquire → daviddias (on 2016-12-07) provenance

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

v0.3.0

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: daviddias → dignifiedquire (on 2016-12-05) provenance

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

v0.2.0

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: dignifiedquire → daviddias (on 2016-10-24) provenance

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

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