linkedom
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 | encoded-string-file:worker.js | AI (source-diff): Long string is the generated htmlDecodeTree entity map, not a payload. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes the bundled entity decode-map; benign, stable across versions. | ai | |
| dependencies | unvetted-peer-dep:canvas | AI (dependencies): canvas is a well-known optional peer dependency for native canvas rendering; no security concern for this package. | ai | |
| phantom-deps | phantom-dep:html-escaper | AI (phantom-deps): html-escaper is a declared runtime dependency in package.json; the phantom-dep finding is a false positive likely due to indirect/bundled usage patterns in linkedom. | ai | |
| dependencies | unvetted-dep:uhyphen | AI (dependencies): uhyphen is a small, well-known utility by the same author (webreflection); no security concern for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.18.13 | 5 / 8 | |
| 0.18.12 | 5 / 8 | |
| 0.18.11 | 5 / 8 | |
| 0.18.10 | 5 / 8 | |
| 0.18.9 | 5 / 8 | |
| 0.18.8 | 5 / 8 | |
| 0.18.7 | 5 / 8 | |
| 0.18.6 | 5 / 8 | |
| 0.18.5 | 5 / 8 | |
| 0.18.4 | 5 / 8 | |
| 0.18.3 | 5 / 8 | |
| 0.18.2 | 5 / 8 | |
| 0.18.1 | 5 / 8 | |
| 0.18.0 | 5 / 8 |
v0.18.13
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.