← Home

@osdk/shared.net.platformapi

npm Repository Homepage
11
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

sauravsanjpalantirericanderson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Palantir migrated publishing to GitHub Actions with SLSA attestation; this is a legitimate CI/CD transition. ai
publish-pattern new-deps-added AI (publish-pattern): @osdk/shared.client2 is a first-party Palantir OSDK package from the same monorepo. ai
dependencies unvetted-dep:@osdk/shared.net.errors AI (dependencies): Sibling package from the same Palantir osdk-ts monorepo; stable false positive for this package family. ai

Versions (showing 11 of 11)

Version Deps Published
1.7.0 3 / 4
1.6.0 3 / 4
0.3.3 3 / 4
0.3.2 3 / 4
0.3.1 2 / 4
0.3.0 2 / 4
0.2.3 2 / 4
0.2.2 2 / 4
0.2.1 2 / 4
0.2.0 2 / 4
0.1.0 2 / 1

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

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