← Home

tinylicious

npm Repository Homepage
3
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ms-fluid-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Microsoft FluidFramework monorepo; version gaps are expected across the many sub-packages in this ecosystem. ai
semgrep semgrep:base64-decode AI (semgrep): Decoding git blob content for HTTP response; standard git storage pattern, not a payload concern. ai
phantom-deps phantom-dep:@fluidframework/protocol-base AI (phantom-deps): Sibling @fluidframework package; referenced in config files as expected for monorepo structure. ai
phantom-deps phantom-dep:@fluidframework/server-services-telemetry AI (phantom-deps): Sibling @fluidframework package; referenced in config files as expected for monorepo structure. ai

Versions (showing 3 of 3)

Version Deps Published
7.0.1 33 / 28
7.0.0 33 / 28
6.0.1 33 / 28

v7.0.1

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.

v7.0.0

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.

v6.0.1

1 finding
LOW No provenance attestation provenance

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