← Home

@contrail/document-table

npm
10
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

grant.hallbrian.lindauercfvibeiqbtosadopraterchris_vibeiqzileevamattvitellomazairajprashantvibeiqkartikisahuadamvibeiqzachsibert_vibeiqjaime-vibeiqmelba.lewisricardojsiscolrakeshvibeiqvadim-kozdanielurchuknwilde-vibeiqashutoshvibeiqraghuvibeiq

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainers share the same -vibeiq org suffix; consistent with internal team rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainer also from -vibeiq org; consistent with internal handoff, not takeover. ai
bogus-package bogus-package AI (bogus-package): Internal @contrail-scoped library; sparse metadata is expected for org-internal packages. ai
phantom-deps phantom-dep:@contrail/types AI (phantom-deps): Same-org scoped dep; likely used transitively or via type-only imports in this package. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): Known implicit dependency for TypeScript decorators; stable false positive for this package. ai
phantom-deps phantom-dep:@contrail/actions AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for org-internal packages. ai

Versions (showing 10 of 10)

Version Deps Published
1.2.1 5 / 9
1.0.20 5 / 8
1.0.19 5 / 8
1.0.18 5 / 8
1.0.17 5 / 8
1.0.16 5 / 8
1.0.14 5 / 8
1.0.12 5 / 8
1.0.6 5 / 8
1.0.5 5 / 8

v1.2.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.

v1.0.20

1 finding
LOW No provenance attestation provenance

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

v1.0.19

1 finding
LOW No provenance attestation provenance

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

v1.0.18

1 finding
LOW No provenance attestation provenance

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

v1.0.17

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.

v1.0.16

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.

v1.0.14

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.

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

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

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