← Home

@ewanc26/tid

npm Repository Homepage
8
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

ewanc26

Keywords

atprotoblueskytidtimestampidentifierlexicon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Small utility with no install scripts or runtime deps; provenance gap is low risk for this package. ai
license copyleft-license:AGPL-3.0-only AI (license): AGPL-3.0 is an intentional license choice by the author; not a security concern. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped AT Protocol utility; name similarity to uuid is coincidental, not impersonation. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped AT Protocol utility; name similarity to zod is coincidental, not impersonation. ai

Versions (showing 8 of 8)

Version Deps Published
1.1.3 0 / 2
1.1.2 0 / 2
1.1.1 0 / 2
1.1.0 0 / 2
1.0.3 0 / 2
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2

v1.1.3

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.

v1.1.2

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: ewanc26.

LOW No provenance attestation provenance

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

v1.1.1

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: ewanc26.

LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.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.