← Home

@phila/phila-ui-tooltip

npm
11
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

cirinocarvalhom-atiaajrothwellphillypackage

Keywords

uitooltipvuecomponent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/index.js AI (source-diff): Vite/esbuild bundled component output, not true obfuscation. ai
phantom-deps phantom-dep:@phila/phila-ui-button AI (phantom-deps): Same-org sibling UI component, likely used via re-export. ai
phantom-deps phantom-dep:@phila/phila-ui-core AI (phantom-deps): Same-org scoped dependency; expected for UI component library. ai
bogus-package bogus-package AI (bogus-package): Monorepo internal package; missing metadata is normal, not spam. ai

Versions (showing 11 of 11)

Version Deps Published
0.1.1 2 / 11
0.1.0 3 / 8
0.0.15 2 / 8
0.0.14 2 / 8
0.0.11 2 / 8
0.0.10 2 / 8
0.0.8 2 / 8
0.0.7 2 / 8
0.0.6 2 / 8
0.0.5 2 / 8
0.0.4 2 / 8

v0.1.1

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: phillypackage.

HIGH New obfuscated file: dist/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.0.14

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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