fluent-ffmpeg
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Stale 3376-day-old publisher change, long since stable; not a takeover signal. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived stable package; dormancy followed by normal maintenance releases. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): which is a common, benign utility dep, not suspicious. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Core functionality: wraps ffmpeg/ffprobe via child_process; expected and stable across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Documented preset-loader pattern; user-controlled path, not attacker-controlled in normal use. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 2 / 4 | |
| 2.1.2 | 2 / 3 | |
| 2.1.1 | 2 / 3 | |
| 2.1.0 | 2 / 3 | |
| 2.0.1 | 1 / 6 |
v2.1.2
2 findingsThis version was published by a different npm account (rhodgkins) than the most recent previously approved version (njoyard) on 2017-04-23. It has since remained available on npm for 3376 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account (rhodgkins) than the most recent previously approved version (njoyard) on 2017-04-23. It has since remained available on npm for 3376 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.