@atcute/oauth-node-client No license 8 versions

@atcute/oauth-node-client

npm Repository

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

externdefs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@badrap/valita	AI (phantom-deps): Listed as a direct dependency in package.json; phantom-dep heuristic false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@atcute/identity	AI (phantom-deps): Same-org sibling package listed as a dependency; phantom-dep heuristic false positive for this monorepo package.	ai	2026/05/20

Versions (showing 8 of 8)

Version	Deps	Published
2.0.0	10 / 2	2026-05-09
1.1.1	10 / 2	2026-05-08
1.1.0	10 / 2	2026-01-30
1.0.0	10 / 2	2026-01-30
0.1.3	10 / 2	2025-12-22
0.1.2	10 / 2	2025-12-15
0.1.1	10 / 2	2025-12-14
0.1.0	10 / 2	2025-12-13

v2.0.0

1 finding

LOW No provenance attestation provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

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

v0.1.2

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