@nectary/assets
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in bundled lottie-web animation expression engine — documented legitimate use for AE expression evaluation. | ai | |
| phantom-deps | phantom-dep:lottie-web | AI (phantom-deps): lottie-web is bundled into the package output rather than imported directly; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped convention; stable false positive for this scoped package. | ai | |
| phantom-deps | phantom-dep:dts-bundle-generator | AI (phantom-deps): Build tooling dependency referenced in config, not runtime import; stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.6.14 | 3 / 12 | |
| 3.6.9 | 3 / 12 | |
| 3.4.2 | 3 / 12 | |
| 3.4.1 | 3 / 12 |
v3.6.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivercarlsson) than the most recent previously approved version (pbricout) on 2026-06-01, but olivercarlsson is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.