openapi-merge
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Common utility dep likely used in compiled dist; false positive on source scan. | ai | |
| phantom-deps | phantom-dep:ts-is-present | AI (phantom-deps): Small utility lib plausibly used in compiled output; not a malware indicator. | ai | |
| phantom-deps | phantom-dep:atlassian-openapi | AI (phantom-deps): Core OpenAPI type dep for this tool; scan misses compiled usage. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env metadata change only; no behavioral signal for this trusted package. | ai | |
| provenance | no-provenance | AI (provenance): Established package (2175 days old) published before Sigstore provenance was widely adopted. No other risk signals present. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 3 / 11 | |
| 1.3.2 | 3 / 11 | |
| 1.3.1 | 3 / 11 | |
| 1.3.0 | 3 / 12 | |
| 1.2.1 | 3 / 12 | |
| 1.2.0 | 3 / 12 | |
| 1.1.33 | 3 / 13 | |
| 1.0.32 | 3 / 13 | |
| 1.0.29 | 3 / 13 | |
| 1.0.25 | 3 / 13 | |
| 1.0.23 | 3 / 13 | |
| 1.0.22 | 3 / 13 | |
| 1.0.18 | 3 / 13 | |
| 1.0.17 | 3 / 13 | |
| 1.0.16 | 3 / 13 | |
| 1.0.15 | 3 / 13 | |
| 1.0.14 | 3 / 13 |
v1.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rmassaioli.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rmassaioli.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rmassaioli.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rmassaioli.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rmassaioli.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.