← Home

@freik/media-core

npm Repository Homepage

Web and NodeJS compatible media stuff

14
Versions
Unlicense
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

freik

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): No behavioral change; established publisher, likely local build env variance. ai
publish-pattern dormant-publish AI (publish-pattern): Established package with clean publisher history; dormancy followed by minor version bump with no material changes is low risk. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires in bun-minified CJS bundle boilerplate; stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Established utility package in a monorepo; sparse README and no keywords are cosmetic, not indicative of spam. ai

Versions (showing 14 of 14)

Version Deps Published
0.16.10 1 / 6
0.16.9 1 / 6
0.16.7 1 / 6
0.16.5 1 / 6
0.16.4 1 / 6
0.16.3 1 / 6
0.16.2 1 / 6
0.15.1 1 / 6
0.15.0 1 / 6
0.14.26 1 / 6
0.14.19 1 / 6
0.14.18 1 / 6
0.14.16 1 / 6
0.14.13 1 / 11

v0.14.19

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.14.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.