Spectra Assure
Community
warningRisk: Tampering
Scanned: 2 days ago

proto-tinker-wc

latest
prototype - simple demo built from Stencil & Tailwind
License: Permissive (MIT)
New!
Published: 2 days ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
1 components with malware history
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

127.36k
Recorded Downloads Since 2021
Contributor
Declared Dependencies
3
Dependents

Top issues

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. Some open source projects have a history of security lapses that culminated with a publication of one or more malicious component versions. To ensure that repeated supply chain incidents do not occur, the open source project should be closely monitored for up to two years. All software package versions that are published within two years of the malware incident will convey a warning about the history of security incidents tied to the open source project.

Prevalence in npm community

10 packages
found in
Top 100
14 packages
found in
Top 1k
81 packages
found in
Top 10k
90.8k packages
in community

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in npm community

18 packages
found in
Top 100
133 packages
found in
Top 1k
1817 packages
found in
Top 10k
2.98M packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Top behaviors

Prevalence in npm community

Behavior often found in this community (Common)
6 packages
found in
Top 100
45 packages
found in
Top 1k
684 packages
found in
Top 10k
195.24k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
95 packages
found in
Top 100
726 packages
found in
Top 1k
7488 packages
found in
Top 10k
4.56M packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
26 packages
found in
Top 100
134 packages
found in
Top 1k
2067 packages
found in
Top 10k
896.14k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
3 packages
found in
Top 100
41 packages
found in
Top 1k
721 packages
found in
Top 10k
248.69k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
18 packages
found in
Top 100
133 packages
found in
Top 1k
1817 packages
found in
Top 10k
2.98M packages
in community

Top vulnerabilities

No vulnerabilities found.