← Home

@duetds/tokens

npm

This package includes Duet Design Tokens and related utilities.

87
Versions
SEE LICENSE IN LICENSE.md
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

lahitapiolalennukasimir-dkaeremannistoleodka

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Stale change (498d live), consistent transfer not takeover, publisher has strong track record. ai
maintainer-change maintainer-removed AI (maintainer-change): Part of same benign transfer as maintainer-added. ai
provenance publisher-changed-stale AI (provenance): Long-stable publisher change, no takeover behavior observed. ai
provenance publisher-changed AI (provenance): New publisher lahitapiola matches the package's own author/bugs domain (lahitapiola.fi); consistent with org account transition. ai

Versions (showing 87 of 87)

Version Deps Published
5.1.0 0 / 4
5.0.1 0 / 5
5.0.0 0 / 5
4.1.10 0 / 5
4.1.9 0 / 5
4.1.8 0 / 5
4.1.7 0 / 5
4.1.6 0 / 5
4.1.5 0 / 5
4.1.4 0 / 5
4.1.3 0 / 5
4.1.2 0 / 5
4.1.1 0 / 5
4.1.0 0 / 5
4.0.109 0 / 5
4.0.108 0 / 5
4.0.107 0 / 5
4.0.106 0 / 5
4.0.105 0 / 5
4.0.104 0 / 5
4.0.103 0 / 5
4.0.102 0 / 5
4.0.101 0 / 5
4.0.100 0 / 5
4.0.99 0 / 5
4.0.98 0 / 5
4.0.97 0 / 5
4.0.96 0 / 5
4.0.95 0 / 5
4.0.94 0 / 5
4.0.93 0 / 5
4.0.92 0 / 5
4.0.91 0 / 5
4.0.90 0 / 5
4.0.89 0 / 5
4.0.88 0 / 5
4.0.87 0 / 5
4.0.86 0 / 5
4.0.85 0 / 5
4.0.84 0 / 5
4.0.83 0 / 5
4.0.82 0 / 5
4.0.81 0 / 5
4.0.80 0 / 5
4.0.79 0 / 5
4.0.78 0 / 5
4.0.77 0 / 5
4.0.76 0 / 5
4.0.75 0 / 5
4.0.74 0 / 5
4.0.73 0 / 5
4.0.72 0 / 5
4.0.71 0 / 5
4.0.70 0 / 5
4.0.69 0 / 5
4.0.68 0 / 5
4.0.67 0 / 5
4.0.66 0 / 5
4.0.65 0 / 5
4.0.64 0 / 5
4.0.63 0 / 5
4.0.62 0 / 5
4.0.61 0 / 5
4.0.60 0 / 5
4.0.59 0 / 5
4.0.58 0 / 5
4.0.57 0 / 5
4.0.56 0 / 5
4.0.55 0 / 5
4.0.54 0 / 5
4.0.53 0 / 5
4.0.52 0 / 5
4.0.51 0 / 7
4.0.50 0 / 7
4.0.49 0 / 7
4.0.48 0 / 7
4.0.47 0 / 7
4.0.46 0 / 7
4.0.45 0 / 7
4.0.44 0 / 7
4.0.43 0 / 7
4.0.42 0 / 7
4.0.41 0 / 7
4.0.40 0 / 7
4.0.39 0 / 7
4.0.38 0 / 7
4.0.37 0 / 7

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.0.74

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → kasimir-dka (on 2025-04-30, known maintainer) provenance

This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-04-30, but kasimir-dka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.73

1 finding
LOW No provenance attestation provenance

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

v4.0.72

2 findings
MEDIUM Publisher changed: lahitapiola → kasimir-dka (on 2025-03-31, unremoved on npm for 473d) provenance

This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-31. It has since remained available on npm for 473 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v4.0.71

1 finding
LOW No provenance attestation provenance

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

v4.0.70

2 findings
MEDIUM Publisher changed: lahitapiola → kasimir-dka (on 2025-03-13, unremoved on npm for 491d) provenance

This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-13. It has since remained available on npm for 491 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v4.0.69

2 findings
MEDIUM Publisher changed: lahitapiola → kasimir-dka (on 2025-03-06, unremoved on npm for 498d) provenance

This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-06. It has since remained available on npm for 498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v4.0.68

1 finding
LOW No provenance attestation provenance

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

v4.0.67

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2025-02-05, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2025-02-05, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.66

1 finding
LOW No provenance attestation provenance

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

v4.0.65

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2025-01-20, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2025-01-20, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.64

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → gibasm (on 2025-01-16, known maintainer) provenance

This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2025-01-16, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.63

1 finding
LOW No provenance attestation provenance

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

v4.0.62

1 finding
LOW No provenance attestation provenance

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

v4.0.61

1 finding
LOW No provenance attestation provenance

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

v4.0.60

1 finding
LOW No provenance attestation provenance

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

v4.0.59

1 finding
LOW No provenance attestation provenance

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

v4.0.58

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2024-11-20, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-11-20, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.57

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → gibasm (on 2024-11-05, known maintainer) provenance

This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-11-05, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.56

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2024-10-24, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-10-24, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.55

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → gibasm (on 2024-10-21, known maintainer) provenance

This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-10-21, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.54

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2024-10-14, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-10-14, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.53

1 finding
LOW No provenance attestation provenance

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

v4.0.52

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → gibasm (on 2024-09-23, known maintainer) provenance

This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-09-23, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.51

1 finding
LOW No provenance attestation provenance

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

v4.0.50

1 finding
LOW No provenance attestation provenance

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

v4.0.49

1 finding
LOW No provenance attestation provenance

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

v4.0.48

1 finding
LOW No provenance attestation provenance

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

v4.0.47

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2024-07-02, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-07-02, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.46

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2024-06-24, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-06-24, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.45

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → gibasm (on 2024-06-13, known maintainer) provenance

This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-06-13, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.44

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lahitapiola → gibasm (on 2024-06-06, known maintainer) provenance

This version was published by a different npm account (gibasm) than the most recent previously approved version (lahitapiola) on 2024-06-06, but gibasm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.43

1 finding
LOW No provenance attestation provenance

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

v4.0.42

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gibasm → lahitapiola (on 2024-06-03, known maintainer) provenance

This version was published by a different npm account (lahitapiola) than the most recent previously approved version (gibasm) on 2024-06-03, but lahitapiola is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.0.41

1 finding
LOW No provenance attestation provenance

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

v4.0.40

1 finding
LOW No provenance attestation provenance

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

v4.0.39

1 finding
LOW No provenance attestation provenance

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

v4.0.38

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

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.