← Home

@dynamic-labs/iconic

npm Homepage
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jesse-at-dynamicpackaging-at-dynamic-labs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is a documented, legitimate pattern for this org across 655 versions. ai
bogus-package bogus-package AI (bogus-package): Established Dynamic Labs SDK package with 655 versions; sparse README/keywords are cosmetic, not indicative of spam. ai
phantom-deps phantom-dep:url AI (phantom-deps): url is a config-referenced polyfill; stable pattern for this package. ai
phantom-deps phantom-dep:sharp AI (phantom-deps): sharp is a known binary dependency; implicit usage is expected. ai

Versions (showing 8 of 209)

Version Deps Published
4.18.5 3 / 0
4.18.4 3 / 0
4.18.3 3 / 0
4.18.2 3 / 0
4.18.1 3 / 0
4.18.0 3 / 0
4.17.0 3 / 0
4.16.0 3 / 0

v4.18.5

1 finding
LOW No provenance attestation provenance

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

v4.18.4

1 finding
LOW No provenance attestation provenance

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

v4.18.3

1 finding
LOW No provenance attestation provenance

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

v4.18.2

1 finding
LOW No provenance attestation provenance

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

v4.18.1

1 finding
LOW No provenance attestation provenance

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

v4.18.0

1 finding
LOW No provenance attestation provenance

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

v4.17.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.

v4.16.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.