← Home

@tailor-cms/ce-embed-edit

npm

Tailor CMS embed element authoring component

12
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

droguljicee_adminikovacundersc0perkusan00

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:lodash-es AI (phantom-deps): lodash-es is a legitimate declared runtime dependency; phantom-dep firing reflects build artifact analysis, not a real missing/unused dep issue for this package. ai
phantom-deps phantom-dep:validator AI (phantom-deps): validator is a legitimate declared runtime dependency; same reasoning as lodash-es phantom-dep false positive. ai
phantom-deps phantom-dep:@tailor-cms/core-components AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep signal is a false positive for this scoped org package. ai

Versions (showing 12 of 12)

Version Deps Published
2.0.1 3 / 10
2.0.0 3 / 10
0.1.0 3 / 8
0.0.9 3 / 8
0.0.8 2 / 8
0.0.7 2 / 8
0.0.6 3 / 8
0.0.5 3 / 8
0.0.4 1 / 6
0.0.3 0 / 6
0.0.2 0 / 6
0.0.1 0 / 6

v2.0.1

1 finding
LOW No provenance attestation provenance

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

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.

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

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

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