@d3plus/text
A smart SVG text box with line wrapping and automatic font size scaling.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted publisher with consistent repo; likely CI environment change, not a takeover signal. | ai | |
| source-diff | encoded-string-file:umd/d3plus-text.full.js | AI (source-diff): Base64 string is UAX#14 line-break pair table decoded via base64js; benign bundled data, stable across versions. | ai | |
| source-diff | encoded-string-file:umd/d3plus-text.full.min.js | AI (source-diff): Same base64 line-break table in minified UMD bundle; benign bundled data. | ai | |
| phantom-deps | phantom-dep:d3-selection | AI (phantom-deps): d3-selection is a declared dependency used in config/build files; phantom-dep heuristic fires but it's a legitimate dep. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped d3plus package; string distance match to 'next' is coincidental, no impersonation intent. | ai | |
| phantom-deps | phantom-dep:d3-transition | AI (phantom-deps): d3-transition is a declared dependency used in config/build files; phantom-dep heuristic fires but it's a legitimate dep. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped d3plus package; string distance match to 'nuxt' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped d3plus package; string distance match to 'jest' is coincidental. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.1.6 | 5 / 0 | |
| 3.1.5 | 5 / 0 | |
| 3.1.4 | 5 / 0 | |
| 3.1.3 | 5 / 0 | |
| 3.1.2 | 5 / 0 | |
| 3.1.1 | 5 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.16 | 4 / 0 | |
| 3.0.15 | 4 / 0 | |
| 3.0.14 | 4 / 0 | |
| 3.0.13 | 4 / 0 | |
| 3.0.12 | 4 / 0 | |
| 3.0.11 | 4 / 0 | |
| 3.0.10 | 4 / 0 | |
| 3.0.9 | 4 / 0 | |
| 3.0.8 | 4 / 0 | |
| 3.0.7 | 4 / 0 | |
| 3.0.6 | 4 / 0 | |
| 3.0.5 | 4 / 0 | |
| 3.0.4 | 4 / 0 | |
| 3.0.3 | 4 / 0 | |
| 3.0.2 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 |
v3.1.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: davelandry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
2 findingsPackage name '@d3plus/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.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: davelandry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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: davelandry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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: davelandry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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: davelandry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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: davelandry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified 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.
v3.0.15
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified 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.
v3.0.14
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified 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.
v3.0.13
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified 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.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.