@sap/artifact-management
Artifact Management on SAP BTP facilitates the generation of project metadata comprising of multiple modules of different technologies, bundles the module into one single deployment artifact and supports one click deploy to Cloud Foundry
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vscode-uri | AI (phantom-deps): vscode-uri is a declared runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established SAP package with long history; lack of Sigstore provenance is consistent across all versions. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.53.4 | 18 / 36 | |
| 1.53.3 | 19 / 37 | |
| 1.53.2 | 20 / 37 | |
| 1.53.1 | 20 / 37 | |
| 1.52.0 | 19 / 37 | |
| 1.51.0 | 19 / 37 | |
| 1.50.0 | 19 / 37 | |
| 1.49.1 | 19 / 37 | |
| 1.49.0 | 19 / 37 | |
| 1.48.0 | 19 / 37 | |
| 1.47.10 | 19 / 37 | |
| 1.47.4 | 19 / 37 | |
| 1.47.0 | 19 / 37 | |
| 1.46.0 | 19 / 37 | |
| 1.45.1 | 19 / 37 | |
| 1.44.1 | 15 / 36 | |
| 1.44.0 | 15 / 36 | |
| 1.43.1 | 15 / 36 | |
| 1.43.0 | 15 / 36 | |
| 1.42.1 | 15 / 36 | |
| 1.42.0 | 15 / 36 | |
| 1.41.0 | 15 / 36 | |
| 1.40.1 | 15 / 36 | |
| 1.40.0 | 15 / 36 | |
| 1.39.1 | 15 / 36 | |
| 1.39.0 | 15 / 36 | |
| 1.38.0 | 15 / 36 | |
| 1.37.0 | 15 / 36 | |
| 1.36.2 | 15 / 36 | |
| 1.36.1 | 15 / 36 | |
| 1.36.0 | 15 / 36 | |
| 1.35.0 | 15 / 36 |
v1.53.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.