@ipld/dag-cbor
JS implementation of DAG-CBOR
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a legitimate bootstrap version for this established IPLD package by a known maintainer; not indicative of malicious intent. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): All added maintainers (lidel, alanshaw, vascosantos, achingbrain, rvagg) are recognized IPFS/IPLD ecosystem contributors; this reflects normal collaborative project governance. | ai | |
| provenance | publisher-changed | AI (provenance): rvagg (Rod Vagg) is the listed package author and a well-known IPLD/Node.js contributor; the publisher transition from mikeal is a legitimate handoff within the IPLD org. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of CJS/ESM dual build output, TypeScript type definitions, and test infrastructure — all consistent with the new ipjs build pipeline. | ai | |
| provenance | missing-githead | AI (provenance): Package underwent a major build system migration (ipjs tooling, dual ESM/CJS output). Missing gitHead reflects changed publish environment, not malicious activity. Stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): cborg and multiformats are established IPLD ecosystem packages replacing borc/@ipld/is-circular. Legitimate dependency modernization, not suspicious injection. | ai | |
| dependencies | unvetted-dep:borc | AI (dependencies): borc is the standard CBOR library used throughout the IPFS/IPLD ecosystem; its use in dag-cbor is expected and legitimate across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; no provenance is expected for this era and publisher history is clean. | ai | |
| dependencies | unvetted-dep:cborg | AI (dependencies): cborg is the standard CBOR codec used throughout the IPFS/IPLD ecosystem and is the expected dependency for dag-cbor; not suspicious. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 2 / 2 | |
| 10.0.0 | 2 / 2 | |
| 9.2.7 | 2 / 2 | |
| 9.2.6 | 2 / 2 | |
| 9.2.5 | 2 / 2 | |
| 9.2.4 | 2 / 2 | |
| 9.2.3 | 2 / 2 | |
| 9.2.2 | 2 / 2 | |
| 9.2.1 | 2 / 2 | |
| 9.2.0 | 2 / 2 | |
| 9.1.0 | 2 / 2 | |
| 9.0.8 | 2 / 2 | |
| 9.0.7 | 2 / 2 | |
| 9.0.6 | 2 / 2 | |
| 9.0.5 | 2 / 2 | |
| 9.0.4 | 2 / 2 | |
| 9.0.3 | 2 / 2 | |
| 9.0.2 | 2 / 2 | |
| 9.0.1 | 2 / 2 | |
| 9.0.0 | 2 / 3 | |
| 8.0.1 | 2 / 3 | |
| 8.0.0 | 2 / 3 | |
| 7.0.3 | 2 / 9 | |
| 7.0.2 | 2 / 9 | |
| 7.0.1 | 2 / 9 | |
| 7.0.0 | 2 / 9 | |
| 6.0.15 | 2 / 9 | |
| 6.0.14 | 2 / 8 | |
| 6.0.13 | 2 / 8 | |
| 6.0.12 | 2 / 8 | |
| 6.0.11 | 2 / 8 | |
| 6.0.10 | 2 / 8 | |
| 6.0.9 | 2 / 8 | |
| 6.0.8 | 2 / 8 | |
| 6.0.7 | 2 / 8 | |
| 6.0.6 | 2 / 8 | |
| 6.0.5 | 2 / 8 | |
| 6.0.4 | 2 / 8 | |
| 6.0.3 | 2 / 8 | |
| 6.0.2 | 2 / 8 | |
| 6.0.1 | 2 / 8 | |
| 6.0.0 | 2 / 8 | |
| 5.0.5 | 2 / 8 | |
| 5.0.4 | 2 / 8 | |
| 5.0.3 | 2 / 8 | |
| 5.0.2 | 2 / 8 | |
| 5.0.1 | 2 / 8 | |
| 5.0.0 | 2 / 8 | |
| 4.0.0 | 2 / 7 | |
| 3.0.0 | 2 / 6 | |
| 2.0.3 | 3 / 5 |
v10.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
2 findingsThis version was published by a different npm account than previous versions on 2022-08-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
2 findingsThis version was published by a different npm account than previous versions on 2022-05-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-03-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-12-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
2 findingsThis version was published by a different npm account than previous versions on 2021-12-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mikeal.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.