multicodec
JavaScript implementation of the multicodec specification
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 from adding TypeScript .d.ts declaration files for the codec table; expected for this package. | ai | |
| source-diff | obfuscated-file:dist/src/generated-types.d.ts | AI (source-diff): Auto-generated TypeScript declaration file with long union types for codec constants; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/src/index.d.ts | AI (source-diff): Auto-generated TypeScript declaration file with long union types for codec names; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/src/int-table.d.ts | AI (source-diff): Auto-generated TypeScript declaration file for codec int-table mappings; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/src/print.d.ts | AI (source-diff): Auto-generated TypeScript declaration file for codec print mappings; not obfuscated. | ai | |
| source-diff | obfuscated-file:src/generated-types.d.ts | AI (source-diff): Auto-generated TypeScript declaration file with long union type of codec constants; not obfuscated. Comment says generated by tools/update-table.js. | ai | |
| source-diff | obfuscated-file:dist/src/maps.d.ts | AI (source-diff): Auto-generated TypeScript type map declaration for codec constants; long lines from many entries, not obfuscation. | ai | |
| source-diff | obfuscated-file:src/generated-types.ts | AI (source-diff): Auto-generated TypeScript type union file from tools/update-table.js. Long lines are codec constant name unions, not obfuscation. Stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): achingbrain is a known IPFS/multiformats maintainer listed as contributor; legitimate team transition from hacdias. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 2 / 5 | |
| 3.2.0 | 2 / 5 | |
| 3.1.1 | 2 / 5 | |
| 3.1.0 | 2 / 5 | |
| 3.0.1 | 2 / 4 | |
| 3.0.0 | 2 / 3 | |
| 2.1.3 | 2 / 3 | |
| 2.1.2 | 2 / 4 | |
| 2.1.1 | 2 / 4 | |
| 2.1.0 | 2 / 3 | |
| 2.0.4 | 2 / 3 | |
| 2.0.3 | 2 / 3 | |
| 2.0.2 | 2 / 3 | |
| 2.0.1 | 2 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.0.4 | 2 / 5 | |
| 1.0.3 | 2 / 5 | |
| 1.0.2 | 2 / 5 | |
| 1.0.1 | 2 / 5 | |
| 1.0.0 | 1 / 5 | |
| 0.5.7 | 1 / 5 | |
| 0.5.6 | 1 / 5 | |
| 0.5.5 | 1 / 4 | |
| 0.5.4 | 1 / 4 | |
| 0.5.3 | 1 / 4 | |
| 0.5.1 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.7 | 1 / 4 | |
| 0.2.6 | 1 / 4 | |
| 0.2.5 | 1 / 4 | |
| 0.2.4 | 1 / 4 | |
| 0.2.3 | 1 / 4 | |
| 0.1.9 | 1 / 4 | |
| 0.1.8 | 1 / 4 | |
| 0.1.7 | 1 / 3 | |
| 0.1.6 | 1 / 3 | |
| 0.1.5 | 1 / 3 | |
| 0.1.4 | 1 / 3 | |
| 0.1.3 | 1 / 3 | |
| 0.1.2 | 1 / 3 | |
| 0.1.1 | 1 / 3 | |
| 0.1.0 | 1 / 3 | |
| 0.0.1 | 1 / 2 |
v3.2.1
2 findingsThis version was published by a different npm account than previous versions on 2021-09-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-30. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-06-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.