@tresjs/core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vue/devtools-api | AI (phantom-deps): @vue/devtools-api is a declared runtime dependency; phantom-dep false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions as part of adopting SLSA provenance via CI/CD automation. SLSA attestation confirms legitimate pipeline publishing; this is a stable, expected pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @tresjs/core is the core package of the TresJS ecosystem (Vue+Three.js renderer), not a typosquat of 'cors'. The scoped namespace and 160-version history confirm legitimacy. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.8.1 | 4 / 27 | |
| 5.8.0 | 4 / 27 | |
| 5.7.0 | 4 / 27 | |
| 5.6.0 | 4 / 27 | |
| 5.5.0 | 4 / 27 | |
| 5.4.1 | 4 / 27 | |
| 5.4.0 | 4 / 27 | |
| 5.3.3 | 4 / 27 | |
| 5.3.2 | 4 / 27 | |
| 5.3.1 | 4 / 27 | |
| 5.3.0 | 4 / 27 | |
| 5.2.1 | 4 / 27 | |
| 5.2.0 | 4 / 27 | |
| 5.1.1 | 5 / 26 | |
| 5.1.0 | 4 / 25 | |
| 5.0.3 | 4 / 38 | |
| 5.0.2 | 4 / 41 | |
| 5.0.1 | 4 / 41 |
v5.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
2 findingsPackage name '@tresjs/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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: alvarosaburido.
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: alvarosaburido.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.