@heartlandone/vega-telemetry-runtime-metrics
Vega Telemetry Runtime Metrics is collecting more runtime metrics to track various pain points, including component usage, overriding feature flag and public APIs.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:index.js | AI (source-diff): Bundled/minified rollup output, not true obfuscation; benign telemetry logging code. | ai | |
| phantom-deps | phantom-dep:md5 | AI (phantom-deps): Used inside bundled dist, false positive for import detection. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal internal telemetry package; sparse metadata is typical, not spam. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 1 / 0 | |
| 1.0.10 | 1 / 0 | |
| 1.0.8 | 2 / 0 | |
| 1.0.7 | 0 / 0 | |
| 1.0.2 | 2 / 0 | |
| 1.0.0 | 5 / 0 |
v1.0.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: janey.ding1.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: janey.ding1.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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: janey.ding1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.