← Home

@osdk/generator-converters

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

sauravsanjpalantirericandersonericjeney-palantir

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Palantir osdk-ts monorepo packages consistently omit descriptions; not a malware indicator here. ai

Versions (showing 91 of 91)

Version Deps Published
2.51.0 2 / 5
2.50.0 2 / 5
2.49.0 2 / 5
2.48.0 2 / 5
2.47.0 2 / 5
2.46.0 2 / 5
2.45.0 2 / 5
2.44.0 2 / 5
2.43.0 2 / 5
2.42.0 2 / 5
2.41.0 2 / 5
2.40.0 2 / 5
2.39.0 2 / 5
2.38.0 2 / 5
2.37.0 2 / 5
2.36.0 2 / 5
2.35.0 2 / 5
2.34.0 2 / 5
2.32.0 2 / 5
2.31.0 2 / 5
2.30.0 2 / 5
2.29.0 2 / 5
2.28.0 2 / 5
2.27.0 2 / 5
2.26.0 2 / 5
2.25.0 2 / 5
2.24.0 2 / 5
2.23.0 2 / 5
2.22.0 2 / 5
2.21.0 2 / 5
2.20.0 2 / 5
2.19.0 2 / 5
2.18.0 2 / 5
2.17.0 2 / 5
2.16.0 2 / 5
2.15.0 2 / 5
2.14.0 2 / 5
2.13.0 2 / 5
2.12.0 2 / 5
2.8.0 2 / 5
2.7.8 2 / 5
2.7.7 2 / 5
2.7.6 2 / 5
2.7.5 2 / 5
2.7.4 2 / 5
2.7.3 2 / 5
2.7.2 2 / 5
2.7.1 2 / 5
2.7.0 2 / 5
2.6.3 2 / 5
2.6.2 2 / 5
2.6.1 2 / 5
2.6.0 2 / 5
2.5.7 2 / 5
2.5.6 2 / 5
2.5.5 2 / 5
2.5.4 2 / 5
2.5.3 2 / 5
2.5.2 2 / 5
2.5.1 2 / 5
2.5.0 2 / 5
2.4.2 2 / 5
2.4.1 2 / 5
2.4.0 2 / 5
2.3.4 2 / 5
2.3.3 2 / 5
2.3.2 2 / 5
2.3.1 2 / 5
2.3.0 2 / 5
2.2.1 2 / 5
2.2.0 2 / 5
2.1.5 2 / 5
2.1.4 2 / 5
2.1.3 2 / 5
2.1.2 2 / 5
2.1.1 2 / 5
2.1.0 2 / 5
2.0.13 3 / 6
2.0.12 3 / 6
2.0.11 2 / 6
2.0.10 2 / 6
2.0.9 2 / 6
2.0.8 2 / 6
2.0.7 2 / 6
2.0.6 2 / 6
2.0.5 2 / 6
2.0.4 2 / 6
2.0.3 2 / 6
2.0.2 2 / 6
2.0.1 2 / 6
2.0.0 2 / 6

v2.51.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.50.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.49.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.48.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.47.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.46.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.45.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.44.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.43.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.42.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.41.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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

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

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

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

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

v2.0.13

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.

v2.0.12

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.

v2.0.11

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.

v2.0.10

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.

v2.0.9

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.

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

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

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

v2.0.5

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.

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

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

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

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

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