Make sure the open source you're using is safe to use
point-at-length
v1.1.0compute a point from an svg path string
npm install point-at-length
Explore Similar Packages
Package Health Score
54 / 100
- Popularity Recognized
- Maintenance Inactive
- Security No known security issues
- Community Limited
Make sure the open source you're using is safe to usePopularity
Recognized
Weekly Downloads (26,089)- Dependents
- 17
- GitHub Stars
- 37
- Forks
- 5
- Contributors
- 5
The npm package point-at-length receives a total of 26,089 downloads a week. As such, we scored point-at-length popularity level to be Recognized.
Based on project statistics from the GitHub repository for the npm package point-at-length, we found that it has been starred 37 times, and that 17 other projects on the ecosystem are dependent on it.
Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.
Security
No known security issues
Security and license risk for significant versions
All VersionsDirect Vulnerabilities
1.0.2
1.1.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
Indirect Vulnerabilities
1.0.2
1.1.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
License Risks
1.0.2
1.1.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
All security vulnerabilities belong to
production dependencies of direct and indirect
packages.
- Security Policy
- No
You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.
We found a way for you to contribute to the project! Looks like point-at-length is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test point-at-length
Maintenance
Inactive
Commit Frequency- Open Issues
- 3
- Merged PR
- 4
- Open PR
- 0
- Last Commit
- 3 years ago
Further analysis of the maintenance status of point-at-length based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.
An important project maintenance signal to consider for point-at-length is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.
In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.
Community
Limited
- Readme.md
- No
- Contributing.md
- No
- Code of Conduct
- No
- Contributors
- 5
- Funding
- No
- License
- MIT
This project has seen only 10 or less contributors.
We found a way for you to contribute to the project! Looks like point-at-length is missing a Code of Conduct.
Embed Package Health Score Badge
Package
- Node.js Compatibility
- not defined
- Age
- 6 years
- Dependencies
- 3 Direct / 3 Total
- Versions
- 5
- Install Size
- 0 B
- Dist-tags
- 1
- # of Files
- 0
- Maintainers
- 2
- TS Typings
- No
We detected a total of 3 direct & transitive dependencies for point-at-length. See the full dependency tree of point-at-length
point-at-length has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.
point-at-length
compute a point from an svg path string
This is like path.getPointAtLength(t) for an svg <path> element, but works
in node + browsers.
If you're in the browser, it's best to use the native svg implementation since that will be faster and more accurate.
example
var point = require('point-at-length');
var pts = point(process.argv.slice(2).join(' '));
var len = pts.length();
for (var i = 0; i <= 10; i++) {
console.log(i / 10, pts.at(i / 10 * len));
}
and then given an svg path:
$ node percent.js m 340.0802,61.38651 c -40.2898,8.22791 \
-62.56591,65.81112 -49.74004,128.6158 12.82587,62.80467 \
55.90207,107.07364 96.19186,98.84572 40.2898,-8.22791 \
62.55966,-65.84175 49.73379,-128.64642 C 423.43994,97.39694 \
380.36999,53.15859 340.0802,61.38651 z m 12.91104,8.55846 c \
22.51488,-4.59795 48.14062,27.6983 57.21553,72.13556 9.0749,44.43726 \
-1.83609,84.19498 -24.35097,88.79294 -22.51489,4.59795 \
-48.11001,-27.70455 -57.18492,-72.14182 -9.0749,-44.43726 \
1.80548,-84.18872 24.32036,-88.78668 z
0 [ 340.0802, 61.38651 ]
0.1 [ 286.4845903594534, 135.39847858871894 ]
0.2 [ 302.1571721534183, 238.7146891719936 ]
0.3 [ 384.5741907293933, 289.20324985412464 ]
0.4 [ 440.01448853962546, 216.81871101620578 ]
0.5 [ 424.995580315864, 113.42989532988953 ]
0.6 [ 344.0127910427327, 60.748668250007114 ]
0.7 [ 409.3069687960253, 137.94315136324377 ]
0.8 [ 387.80154792789017, 230.38180833710817 ]
0.9 [ 329.13606555255416, 160.92824115677908 ]
1 [ 352.99124, 69.94497 ]
methods
var point = require('point-at-length')
var pts = point(svgpath)
Create a new pt instance given svgpath,
an svg path string,
or an array that matches the format returned by
parse-svg-path.
pts.length()
Compute the total length of the path.
This method is based on the output of the getTotalLength() method of
svg path elements.
var xy = pts.at(len)
Compute the [x,y] point xy from a distance len into the geometry.
install
With npm do:
npm install point-at-length
license
MIT
point-at-length versions
| Version | Published | Tag | Node.js Compatability | Licenses | Dependencies | Direct Vulnerabilities | Publisher |
|---|---|---|---|---|---|---|---|
| 1.1.0 | 16 October 2017 | latest | * | MIT | 3 |
| mkaemmerer |
| 1.0.2 | 31 January 2017 | * | MIT | 3 |
| substack | |
| All Versions | |||||||
point-at-length dependencies
Last updated on
12 January-2021, at 19:52 (UTC).