← Home

@01.software/sdk

npm Repository Homepage

01.software SDK

48
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

kdnhyk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/payload-types-BbEEk9Ji.d.cts AI (source-diff): Auto-generated Payload CMS type declaration with long union literals; not obfuscated code. ai
source-diff obfuscated-file:dist/payload-types-BbEEk9Ji.d.ts AI (source-diff): Auto-generated Payload CMS type declaration with long union literals; not obfuscated code. ai
source-diff obfuscated-file:dist/server-Cv0Q4dPQ.d.ts AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. ai
source-diff obfuscated-file:dist/server-C0C8dtms.d.cts AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. ai
source-diff obfuscated-file:dist/server-_zvihptw.d.ts AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not executable obfuscation. ai
source-diff obfuscated-file:dist/server-n3xK4Nks.d.cts AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not executable obfuscation. ai
source-diff obfuscated-file:dist/payload-types-ggU6BNuH.d.ts AI (source-diff): Auto-generated Payload CMS type declarations; long lines are union types, not obfuscation. ai
source-diff obfuscated-file:dist/payload-types-ggU6BNuH.d.cts AI (source-diff): Auto-generated Payload CMS type declarations; long lines are union types, not obfuscation. ai
source-diff obfuscated-file:dist/server-D369bCVJ.d.cts AI (source-diff): TypeScript declaration file generated by tsup bundler; long lines are bundled type exports, not obfuscated code. ai
source-diff obfuscated-file:dist/server-C2Q9R-Lu.d.ts AI (source-diff): TypeScript declaration file generated by tsup bundler; long lines are bundled type exports, not obfuscated code. ai
source-diff obfuscated-file:dist/server-CZrUwqDs.d.cts AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not executable code. ai
source-diff obfuscated-file:dist/server-DULueNYi.d.ts AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not executable code. ai
source-diff obfuscated-file:dist/server-D7FcHj7J.d.ts AI (source-diff): Bundled TypeScript declaration file; long lines are from tsup type bundling, not obfuscation. ai
source-diff obfuscated-file:dist/server-DJcDyOmM.d.cts AI (source-diff): Bundled TypeScript declaration file; long lines are from tsup type bundling, not obfuscation. ai
provenance no-provenance AI (provenance): Package consistently published without provenance; low-risk SDK with no other red flags. ai
dependencies unvetted-dep:@payloadcms/richtext-lexical AI (dependencies): Official PayloadCMS rich-text package; expected dependency for this SDK. ai
dependencies unvetted-dep:payload AI (dependencies): payload is the canonical PayloadCMS framework; legitimate dependency for a CMS SDK. ai
phantom-deps phantom-dep:jose AI (phantom-deps): jose is a declared runtime dep used for JWT handling; phantom-dep heuristic false positive for this package. ai

Versions (showing 48 of 48)

Version Deps Published
0.28.0 9 / 23
0.27.0 9 / 23
0.26.0 9 / 23
0.24.0 9 / 22
0.23.0 9 / 21
0.21.0 9 / 21
0.19.0 9 / 21
0.18.0 9 / 21
0.17.0 9 / 21
0.16.0 9 / 21
0.15.0 9 / 21
0.14.0 9 / 21
0.13.0 9 / 21
0.12.1 9 / 21
0.12.0 9 / 21
0.11.0 9 / 21
0.10.1 9 / 21
0.10.0 9 / 21
0.9.0 9 / 21
0.8.0 9 / 21
0.7.1 9 / 21
0.6.0 9 / 21
0.5.8 9 / 21
0.5.7 9 / 21
0.5.6 9 / 21
0.5.5 9 / 21
0.5.4 9 / 21
0.5.1 7 / 21
0.4.2 6 / 21
0.3.0 6 / 19
0.2.8 4 / 16
0.2.7 4 / 16
0.2.6 4 / 16
0.2.5 4 / 16
0.2.4 4 / 16
0.2.3 4 / 16
0.2.2 4 / 16
0.2.1 4 / 16
0.2.0 4 / 16
0.1.9 4 / 16
0.1.8 4 / 16
0.1.7 4 / 16
0.1.6 4 / 16
0.1.5 4 / 16
0.1.4 4 / 16
0.1.3 4 / 16
0.1.2 4 / 16
0.1.1 4 / 16

v0.28.0

3 findings
HIGH New obfuscated file: dist/server-D369bCVJ.d.cts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server-C2Q9R-Lu.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.27.0

3 findings
HIGH New obfuscated file: dist/server-n3xK4Nks.d.cts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server-_zvihptw.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.26.0

3 findings
HIGH New obfuscated file: dist/server-CZrUwqDs.d.cts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server-DULueNYi.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.24.0

1 finding
INFO No provenance attestation provenance

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

v0.23.0

3 findings
HIGH New obfuscated file: dist/server-DJcDyOmM.d.cts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/server-D7FcHj7J.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.21.0

1 finding
INFO No provenance attestation provenance

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

v0.19.0

1 finding
INFO No provenance attestation provenance

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

v0.17.0

1 finding
INFO No provenance attestation provenance

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

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

v0.15.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.

v0.14.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.

v0.13.0

1 finding
INFO No provenance attestation provenance

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

v0.12.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.

v0.12.0

1 finding
INFO No provenance attestation provenance

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

v0.11.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.

v0.10.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.

v0.10.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.

v0.9.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.

v0.8.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.

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

v0.6.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.

v0.5.8

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

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

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

1 finding
INFO No provenance attestation provenance

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

v0.5.4

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

v0.4.2

3 findings
HIGH New obfuscated file: dist/payload-types-BbEEk9Ji.d.cts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/payload-types-BbEEk9Ji.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.3.0

1 finding
INFO No provenance attestation provenance

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

v0.2.8

1 finding
INFO No provenance attestation provenance

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

v0.2.7

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

INFO No provenance attestation provenance

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

v0.2.6

1 finding
INFO No provenance attestation provenance

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

v0.2.5

1 finding
INFO No provenance attestation provenance

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

v0.2.4

1 finding
INFO No provenance attestation provenance

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

v0.2.3

1 finding
INFO No provenance attestation provenance

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

v0.2.2

1 finding
INFO No provenance attestation provenance

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

v0.2.1

1 finding
INFO No provenance attestation provenance

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

v0.2.0

1 finding
INFO No provenance attestation provenance

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

v0.1.9

1 finding
INFO No provenance attestation provenance

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

v0.1.8

1 finding
INFO No provenance attestation provenance

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

v0.1.7

1 finding
INFO No provenance attestation provenance

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

v0.1.6

1 finding
INFO No provenance attestation provenance

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

v0.1.5

1 finding
INFO No provenance attestation provenance

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

v0.1.4

1 finding
INFO No provenance attestation provenance

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

v0.1.3

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

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